-
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 external registry issues #1230
Conversation
Added breaking change since this will be minorly breaking as is for people who use an in cluster external registry |
Dropping the breaking change label after some more testing. It will update the state correctly on upgrade. |
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.
just a couple notes
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.
🎉
## Description This refactors a lot of how we interact with registries (particularly external ones) to address the following bugs: - The inability to use registries external to the current cluster - The inability to set the NodePort of the internal Zarf registry ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
Description
This refactors a lot of how we interact with registries (particularly external ones) to address the following bugs:
Related Issue
Fixes #N/A
Type of change
Checklist before merging