-
Notifications
You must be signed in to change notification settings - Fork 174
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
Make init package idempotent #751
Conversation
c13f0a2
to
4df2995
Compare
@jeff-mccoy @JasonvanBrackel @YrrepNoj thoughts on splitting the test for this into its own task under #774? If we get this in where we can run double inits we could add a new ci workflow for handling upgrade testing. |
@Racer159 I'm totally fine with that |
Oops. lol |
Agree with @Racer159. Fine with that |
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. Will need #774 eventually
Description
This PR resolves issues with re-running
zarf init
on an existing zarf cluster. Specifically, it resolves an issue with the injector not excluding itself from the mutating webhook and also the seed registry not using persistence causing issues with upgrades.