-
Notifications
You must be signed in to change notification settings - Fork 278
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
Enable authentication to private registries in helm-controller #4114
Comments
Fixed in v1.27.2 but not tested by QA - adding to next milestone. |
Validated using rke2 version v1.27.5+rke2r1Using the test manifest k3s-io/helm-controller#192 (comment)
From the logs:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The HelmChart custom resource does not support authenticating to private repositories. Currently, the HelmChart custom resource does not provide any mechanisms to allow private helm chart repository authentication.
Describe the solution you'd like
The HelmChart custom resource should have an 'authentication secret' field to allow users to provide a secret name containing username and password credentials for private helm chart repository authentication.
Describe alternatives you've considered
No current workarounds
Additional context
Related k3s.io upstream Github issues:
can't use private repos
ability to add private registries
Potentially Affected Code:
HelmChartSpec struct declaration
helm-controller job initialization
Args passed to helm job container at runtime
Related PRs:
Support private repository with username and password #34: This PR is for klipper-helm. A PR to allow the helm-controller to receive username/password creds would need to accompany it.
This PR was closed as the solution posed too much of a security risk
Related Jira ticket: https://jira.suse.com/browse/SURE-4489
The text was updated successfully, but these errors were encountered: