You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug a clear and concise description of what the bug is.
Helm release is deleted if the source of the Helm chart has changed. (releaseName is set)
Which in my opinion is a terrible bug (unexpected behavior).
Because Helm itself behaves differently.
Let's imagine that I installed a chart with a database (a critical element of the system), but had to fork the upstream chart to urgently fix a critical bug.
I change spec.chart.specюc.hart of HelmRelease and the operator completely deletes the previous Helm release and installs everything again (there will be revision 1).
{"level":"info","ts":"2024-10-27T14:10:16.521Z","msg":"release target configuration changed (chart name): running uninstall for current release","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"hello-world","namespace":"test"},"namespace":"test","name":"hello-world","reconcileID":"4140ba43-337c-430c-aa51-f7713d07b252"}
What's your helm version?
v3.15.3
What's your kubectl version?
v1.30.3
What's the chart version?
2.14.0
What happened?
When only the chart source name was changed, the Helm release was removed and reinstalled.
{"level":"info","ts":"2024-10-27T14:10:16.521Z","msg":"release target configuration changed (chart name): running uninstall for current release","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"hello-world","namespace":"test"},"namespace":"test","name":"hello-world","reconcileID":"4140ba43-337c-430c-aa51-f7713d07b252"}
It would be great if there was at least an option to disable uninstall in such scenario
What you expected to happen?
When the name of the chart source is changed or the chart name changed in the repository, the Helm release is updated, not re-installed. (the revision version of helm release is increased)
(releaseName is set)
Describe the bug a clear and concise description of what the bug is.
Helm release is deleted if the source of the Helm chart has changed. (releaseName is set)
Which in my opinion is a terrible bug (unexpected behavior).
Because Helm itself behaves differently.
Let's imagine that I installed a chart with a database (a critical element of the system), but had to fork the upstream chart to urgently fix a critical bug.
I change spec.chart.specюc.hart of HelmRelease and the operator completely deletes the previous Helm release and installs everything again (there will be revision 1).
{"level":"info","ts":"2024-10-27T14:10:16.521Z","msg":"release target configuration changed (chart name): running uninstall for current release","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"hello-world","namespace":"test"},"namespace":"test","name":"hello-world","reconcileID":"4140ba43-337c-430c-aa51-f7713d07b252"}
What's your helm version?
v3.15.3
What's your kubectl version?
v1.30.3
What's the chart version?
2.14.0
What happened?
When only the chart source name was changed, the Helm release was removed and reinstalled.
{"level":"info","ts":"2024-10-27T14:10:16.521Z","msg":"release target configuration changed (chart name): running uninstall for current release","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"hello-world","namespace":"test"},"namespace":"test","name":"hello-world","reconcileID":"4140ba43-337c-430c-aa51-f7713d07b252"}
It would be great if there was at least an option to disable uninstall in such scenario
What you expected to happen?
When the name of the chart source is changed or the chart name changed in the repository, the Helm release is updated, not re-installed. (the revision version of helm release is increased)
(releaseName is set)
How to reproduce it?
Enter the changed values of values.yaml?
The text was updated successfully, but these errors were encountered: