CSO doesn't support helm hooks

Open
#244 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, helm, kubernetes
Domain
devops, infrastructure

Research direction

Start with CSO's helm template handling and the related issue #153, then inspect how the Calico chart's templates/tigera-operator/00-uninstall.yaml hook is processed. Verify the lifecycle behavior with the tigera-operator v3.28.1 chart; done means pre-delete hooks are not treated as ordinary resources and Calico works without downgrading the chart.

Written by the indexing model from the issue text.

Description

Container

/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 https://github.com/projectcalico/calico/issues/9033.
My workaround is to use chart v3.26.4, where this hook doesn't exist.
IMO we again hit the helm template issue https://github.com/SovereignCloudStack/cluster-stack-operator/issues/153.

Environment:

  • cluster-stack-operator version:
  • Kubernetes version: (use kubectl version)
  • OS (e.g. from /etc/os-release):
Dominant language
Go
Stars
18
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SovereignCloudStack/cluster-stack-operator

All issues in SovereignCloudStack/cluster-stack-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.