-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 ability to pass an explicit registry value to Helm charts #2188
Add ability to pass an explicit registry value to Helm charts #2188
Conversation
Codecov Report
|
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.
In general this looks an ok change.
Few nits:
- Please add unit tests for expliciteRegistry config
- The way we do config changes is a little bit hairy.
- We first merge the PR where we freeze config.
- Then merge the PR with config change.
Can you revert the config freeze change from this PR?
Done, should I open a PR for the config? I left out the |
@dgageot Can we run kokora again? could the time out have something to do with cloudflare's issues yesterday? |
@michaelbeaumont kokoro can't simply be retriggered. The easiest way would be for you to rebase on top of master. |
Pinging @balopat |
sorry @michaelbeaumont, looks like you need one more rebase. once you do that CI should be green and I think this is good to go |
@nkubala Done! |
@nkubala Can we please get this merged 🙏 |
I've run into a problem deploying a chart based on stable/postgresql where an explicit
registry
value is expected when the templates are rendered. I'm not sure how common this pattern is amongst other charts but given that Postgres uses it and it seems reasonable in general, it seemed ok to me to add it as an option to Skaffold.