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
As mentioned in title, default helm function works weird and threats false as undefined and applies default value when I expect false. The Helm community has similar discussions as well: helm/helm#12080
So for the deployment.yaml in the Helm template, the template settings for the following two parameters will cause the value to always be true.
To Reproduce
When installing KubeBlocks charts using helm install and setting parameter values such as --set controllers.workloads.enabled=false, the value will not be set to false.
Expected behavior
For the two parameters mentioned in the description, users should be able to set the desired boolean values, rather than them always being true.
The text was updated successfully, but these errors were encountered:
Describe the bug
As mentioned in title, default helm function works weird and threats false as undefined and applies default value when I expect false. The Helm community has similar discussions as well: helm/helm#12080
So for the
deployment.yaml
in the Helm template, the template settings for the following two parameters will cause the value to always be true.To Reproduce
When installing KubeBlocks charts using helm install and setting parameter values such as
--set controllers.workloads.enabled=false
, the value will not be set to false.Expected behavior
For the two parameters mentioned in the description, users should be able to set the desired boolean values, rather than them always being true.
The text was updated successfully, but these errors were encountered: