-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add --push-ignore-immutable-tag-errors boolean CLI option #2774
Add --push-ignore-immutable-tag-errors boolean CLI option #2774
Conversation
Thanks for the PR here @matheuscscp. If you can rebase your changes here and fix the lint error (snippet below) we should be able to merge this. To fix the below you need to the added
struct{
|
500272c
to
3437165
Compare
Thanks @aaron-prindle! I just rebased and fixed the lint error 👌 |
@matheuscscp thanks for the PR here, can you also add this flag to the README.md section which lists kaniko's CLI flag options: Once that is done we should be able to merge |
3437165
to
03a6911
Compare
@aaron-prindle Done! 👌 |
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.
LGTM, thanks for the PR here @matheuscscp
Thanks for merging this, @aaron-prindle! Can you please cut a release? Thanks 🙏 🙏 🙏 |
@matheuscscp Kaniko v1.21.0 is released now with this change included. Thanks for the PR! |
Description
This change adds the boolean CLI flag
--push-ignore-immutable-tag-errors
for ignoring known tag immutability errors after a push. When the flag istrue
, an error known to be due to a tag immutability feature, e.g. Google Artifact Registry's tag immutability, a push would simply ignore such error and return with success.In my use case we have a Google Artifact Registry with immutable tags enabled, but our CD pipelines may try to build and push the same tag in parallel. Since we ensure on our side that the produced images would necessarily be identical, we would like to be able to ignore such errors and consider the push successful so our pipelines can just move on.
Submitter Checklist
Reviewer Notes
Release Notes
This change adds the boolean CLI flag
--push-ignore-immutable-tag-errors
for ignoring known tag immutability errors after a push. When the flag istrue
, an error known to be due to a tag immutability feature, e.g. Google Artifact Registry's tag immutability, a push would simply ignore such error and return with success.