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
Is your feature request related to a problem? Please describe.
A chart with a PVC is unlikely to work when the --force option is used because the client side apply fails to overwrite dynamic values from the server.
emosbaugh
changed the title
The use of --force when applying helm upgrades causes issues with some charts
Add DisableForce bool to ClusterConfig Chart object as well as Chart CR to disable the use of --force flag when running helm upgrade
Aug 15, 2024
emosbaugh
changed the title
Add DisableForce bool to ClusterConfig Chart object as well as Chart CR to disable the use of --force flag when running helm upgrade
Add option to disable the use of --force flag when running helm upgrade extensions
Aug 15, 2024
Is your feature request related to a problem? Please describe.
A chart with a PVC is unlikely to work when the
--force
option is used because the client side apply fails to overwrite dynamic values from the server.Relevant helm issue:
helm/helm#11729 (comment)
Repro steps
install chart
upgrade chart
See the error in the logs
Helm CLI repro
Describe the solution you would like
Add DisableForce boolean to the Chart object in the k0s ClusterSpec as well as the ChartSpec object in the chart CR.
Describe alternatives you've considered
Fork the twuni/docker-registry chart and use a StatefulSet or use helm's
lookup()
function to set the VolumeName and StorageClassName.Additional context
No response
The text was updated successfully, but these errors were encountered: