-
Notifications
You must be signed in to change notification settings - Fork 304
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
helm: accept parameters to globally configure image registry & pull secrets #378
Labels
Comments
It would help our users too 🥺 |
Hello all, @wallyqs, |
Our company also needs a fix for this issue. Any updates? |
#606 will allow for the registry to be overridden on a per-image basis. Could look at adding global next |
Global Image Registry and Pull Policy are supported in nats-1.0.0-beta.0 Global Image pull secrets are not in there yet so I'll leave this open |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enterprises often require private image registries that proxy public ones.
Configuring a different, authenticated registry should be as simple as configuring a custom repository for any common package manager.
We shouldn't have to track down & replace the entire name of every image to add a constant prefix.
Other helm charts commonly do this.
In the bitnami/wordpress chart notice global parameters
global.imageRegistry
global.imagePullSecrets
for global settings alongside higher precedence image-specific parameters
image.registry
image.pullSecrets
to override specific images.
Please do the same for all charts here to simplify deployments?
The text was updated successfully, but these errors were encountered: