Create helm-releases instead of `helm template | kubectl apply -f -`

Open
#153 1 comment 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
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm, kubernetes
Domain
devops, infrastructure

Research direction

Start by locating the code that runs helm template | kubectl apply -f - and read how chart deployments are currently managed. Replace that workflow with Helm releases, then verify that upgrades remove obsolete resources and that Helm capabilities, notes, upgrade, and rollback behavior are preserved.

Written by the indexing model from the issue text.

Description

Container

Helm should be used to create helm-releases. That is the way how helm is supposed to be used. The documentation of helm refers to the scenario where helm is used that way. helm template is useful for debugging but it is not supposed to be used to create the manifests that are then applied to the cluster. helm template lacks important features like capabilities, notes, upgrade and rollback, to just name a few.

In the worst case chart A version 1 deploys a configmap and in version 2 the configmap is changed to a secret. In the current approach the configmap will be stuck in the cluster forever. With helm upgrade, that configmap would be removed.

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.