-
Notifications
You must be signed in to change notification settings - Fork 171
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 agent mutation of new registry #845
Conversation
Is there a reason we wouldn't just add the correct agent ignore label to the pod all the time vs hardcode a special exemption that would still hit the webhook? |
We could do that too (this seemed easier at first). Lemme flip it around. |
@jeff-mccoy done (you were right this time) |
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.
I think we need to use ignore/skip zarf.dev/agent=ignore
here instead. Reason for this is if the agent and registry both died due to node failures, you'd be stuck in a pending state with "patched" waiting for the agent whereas ignore wouldn't depend on the agent existing at all.
Changed |
## Description This is a hotfix related to the image SHASUMs introduced recently to not mutate the zarf registry on a zarf reinit. ## Related Issue Fixes # N/A ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) ## Checklist before merging - [X] (Optional) Changes have been linted locally with [golangci-lint](https://github.com/golangci/golangci-lint). (NOTE: We haven't turned on lint checks in the pipeline yet so linting may be hard if it shows a lot of lint errors in places that weren't touched by changes. Thus, linting is optional right now.) Co-authored-by: Megamind <[email protected]>
Description
This is a hotfix related to the image SHASUMs introduced recently to not mutate the zarf registry on a zarf reinit.
Related Issue
Fixes # N/A
Type of change
Checklist before merging