Open J11522 opened 3 years ago
I think this makes sense and we would love to accept a contribution.
Facing the same issue for private helm/chart repo.
I'm facing this issue when trying to pull helm charts I've created and stored in a Gitlab private registry.
Hey I was able to submit a pull request with code that worked for me to resolve this: https://github.com/aws/aws-cdk/pull/23068
Please let me know if anybody has feedback!
Currently, there is no way of accessing a private helm registry. By adding support for the helm registry login command, we can consume private charts in the same way as on a local cluster.
Use Case
In order to consume and deploy a private helm chart into my EKS cluster.
Proposed Solution
I would propose specifying a secret or secret resolve string in the HelmChartOptions This is then passed to the kubectl handler Lambda function
Prior to calling upgrade I would check if a secret is passed. This needs to be resolved using the secrets manager and the actual login data is passed to the
helm registry login
commandThis is a :rocket: Feature Request