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
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I created a cluster addon with Calico CNI helm chart tigera-operator v3.28.1. This helm chart contains a pre-delete helm hook, which should run only during uninstallation. CSO does helm template so all the resources are created regardless of hook/nohook and Calico doesn't work.
What did you expect to happen:
Helm hooks are executed in the correct stages of the cluster lifecycle.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
A related issue with a similar problem projectcalico/calico#9033.
My workaround is to use chart v3.26.4, where this hook doesn't exist.
IMO we again hit the helm template issue #153.
Environment:
cluster-stack-operator version:
Kubernetes version: (use kubectl version)
OS (e.g. from /etc/os-release):
The text was updated successfully, but these errors were encountered:
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I created a cluster addon with Calico CNI helm chart tigera-operator v3.28.1. This helm chart contains a pre-delete helm hook, which should run only during uninstallation. CSO does
helm template
so all the resources are created regardless of hook/nohook and Calico doesn't work.What did you expect to happen:
Helm hooks are executed in the correct stages of the cluster lifecycle.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
A related issue with a similar problem projectcalico/calico#9033.
My workaround is to use chart v3.26.4, where this hook doesn't exist.
IMO we again hit the
helm template
issue #153.Environment:
kubectl version
)/etc/os-release
):The text was updated successfully, but these errors were encountered: