Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workflows: Skip building cilium-operator image #16501

Merged
merged 1 commit into from Jun 16, 2021

Conversation

pchaigno
Copy link
Member

@pchaigno pchaigno commented Jun 10, 2021

I tested this PR by switching from pull_request_target to pull_request and all tests were passing except for ConformanceAKS and ConformanceEKS. These two were failing with known flakes on flow validation, unrelated to the cilium-operator image.

image

@pchaigno pchaigno added area/CI-improvement Topic or proposal to improve the Continuous Integration workflow release-note/ci This PR makes changes to the CI. labels Jun 10, 2021
@pchaigno pchaigno force-pushed the pr/pchaigno/skip-building-cilium-operator-image branch 8 times, most recently from 6029a30 to 9ee4d8a Compare June 14, 2021 16:57
@pchaigno pchaigno marked this pull request as ready for review June 14, 2021 16:57
@pchaigno pchaigno requested review from a team as code owners June 14, 2021 16:57
Copy link
Member

@nbusseneau nbusseneau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I just hope nobody uses the "multi-IPAM" image in the wild...

@christarazi
Copy link
Member

So now do we expect users to build their own Operator variant if they want to use the latest?

@pchaigno
Copy link
Member Author

So now do we expect users to build their own Operator variant if they want to use the latest?

If they want to use the multi-IPAM image, yes. But they can also use cilium-operator-generic most of the time. In general, I'm not sure we recommend the use of latest images anyway, and the -ci suffix should clarify that these images were intended for CI and nothing else.

We don't need the cilium-operator image in CI, only the
cilium-operator-xxx variants. We therefore don't need to build that
image for every pushes and pull requests.

Signed-off-by: Paul Chaignon <paul@cilium.io>
@pchaigno pchaigno force-pushed the pr/pchaigno/skip-building-cilium-operator-image branch 2 times, most recently from ca5e48f to 4f02ff2 Compare June 15, 2021 14:14
@pchaigno pchaigno added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 15, 2021
@borkmann borkmann merged commit 3c47d70 into master Jun 16, 2021
@borkmann borkmann deleted the pr/pchaigno/skip-building-cilium-operator-image branch June 16, 2021 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI-improvement Topic or proposal to improve the Continuous Integration workflow ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants