Currently, LCM can upgrade private Helm charts only when they are defined through a HelmChart resource that includes the appropriate private repository credentials.
This creates several limitations, as LCM cannot currently:
- Upgrade Helm charts deployed only with
helm install
- Updating a Helm chart to point from a public repository to a private one
These limitations stem from the fact that LCM does not manage or discover chart credentials independently, and instead relies entirely on the associated HelmChart resource to provide them.
To improve flexibility, LCM should support dynamically configuring or updating chart repository credentials during the upgrade process.
This would mitigate any manual steps that users would have to potentially do before triggering upgrade.
Currently, LCM can upgrade private Helm charts only when they are defined through a
HelmChartresource that includes the appropriate private repository credentials.This creates several limitations, as LCM cannot currently:
helm installThese limitations stem from the fact that LCM does not manage or discover chart credentials independently, and instead relies entirely on the associated
HelmChartresource to provide them.To improve flexibility, LCM should support dynamically configuring or updating chart repository credentials during the upgrade process.
This would mitigate any manual steps that users would have to potentially do before triggering upgrade.