-
Notifications
You must be signed in to change notification settings - Fork 165
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-Controller fails to render all Chart dependencies when using aliases #575
Comments
I have some information to add to this: if the aliased charts are referencing the chart at the same version, they're rendered correctly. It seems that only one version of a chart dependency can be rendered at a time. |
Hi @waterbrother, the bug was in |
Hi @souleb That makes sense; thank you for the fast fix! When is the next release scheduled, or how can I be notified when this is released? |
Subscribe to the https://github.com/fluxcd/flux2 releases by clicking the |
Awesome, thanks again! |
Updated via #581, release building. Thanks @waterbrother and @souleb 🙇 |
Describe the bug
When the Flux helm controller renders a Helm chart with aliased Dependencies, only one of the aliased charts is installed to the cluster. It appears to be indeterminate which version of the chart dependency gets installed; the consistent factor is that only one dependency is installed.
Example Chart.yaml:
Result from
kubectl get deploy -n default
:If the Chart is installed with
helm upgrade --install
, the Dependencies are installed as expected:Flux is installing the Chart from a Git source:
Here's the HelmRelease:
FluxCD version:
Kubernetes version:
Steps to reproduce
Expected behavior
A set of resources based on the name of the aliased charts is created.
The text was updated successfully, but these errors were encountered: