-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ability to use private registry for helm deployment #42661
Comments
We could add this ability to rancher-webhook but the setting would not be used unless we also update the rancher server to propagate the value when deploying the rancher-webhook helm chart. You can create a feature request in https://github.com/rancher/rancher project since the rancher pod is responsible for managing the deployment values of rancher-webhook. |
With the changes added here #41142. Users can now pass arbitrary helm values down from Rancher to the Webhook helm release. That means we can update the Webhook chart to support private registry secrets without the need to have additional rancher/rancher updates. |
moving to backlog (unscheduled) |
How can we use a private registry for rancher-webhook? |
When using a private registry to pull image,
the webhook chart / template manifests are missing imagePullSecrets parameters to authenticate against registry.
Should be nice to add in helm templating file:
The text was updated successfully, but these errors were encountered: