-
Notifications
You must be signed in to change notification settings - Fork 919
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
fix(ci): simplify and fix multi-arch image publishing process #2542
fix(ci): simplify and fix multi-arch image publishing process #2542
Conversation
Signed-off-by: Luca Guerra <luca@guerra.sh>
/milestone 0.35.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: ade5420f7b4d07d0e8bdd63c1f4dd8b1d28c2b56
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Refs #2501 |
What type of PR is this?
/kind bug
/kind cleanup
/area CI
What this PR does / why we need it:
This is a refactor and fix of the container image publishing process. There are two major changes:
:x86_64-0.35.0
). This is done because in order to create a multiarch (index
,manifest.list
) manifest easily we need manifests with the referenced digests already published. It is probably possible to do it without (buildx can do something similar) but it may involve a local registry or some more complicated process. I think this is fine for now.docker.io/falcosecurity/falco
) and then adds any additional tags or registries (ECR, latest tags...). This simplifies things especially when the next PR will be published, which is related to signatures with cosign.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Note that the arch specific tags are not pushed to ECR. We can change this behavior
Does this PR introduce a user-facing change?: