←back to thread

Broadcom to discontinue free Bitnami Helm charts

(github.com)
229 points mmoogle | 3 comments | 18 Jul 25 19:29 UTC | HN request time: 0.802s | source
Show context
dpkirchner ◴[18 Jul 25 22:16 UTC] No.44610377[source]▶
Maybe this will finally break me of my habit of using helm charts, period.
replies(4): >>44610605 #>>44610877 #>>44610954 #>>44612370 #
skissane ◴[18 Jul 25 23:26 UTC] No.44610954[source]▶
I’ve never used Helm charts. I learned K8S in a shop in which kustomize is the standard and helm is a permitted exception to the standard, but I just never felt any reason to learn helm. Am I missing out?

Sometimes the limitations of kustomize annoy me, but we find ways to live with them

replies(7): >>44611081 #>>44611452 #>>44611555 #>>44611784 #>>44612267 #>>44612326 #>>44614078 #
1. znpy ◴[19 Jul 25 09:59 UTC] No.44614078[source]▶
Kustomize is nice but you’re missing out on objects lifecycle management.

Kustomize had the issue that it would leave objects dangling in the cluster and you had to manually clean them up of you removed them from your kustomization file.

replies(2): >>44616636 #>>44622759 #
2. pestaa ◴[19 Jul 25 16:02 UTC] No.44616636[source]▶
If you use the kustomize controller from the FluxCD project, you can set it to prune unmanaged objects.

In true GitOps, I think it's should be default on.

3. skissane ◴[20 Jul 25 07:29 UTC] No.44622759[source]▶
This doesn't happen for me, due to ArgoCD–the kustomize YAML is in a PR, and when it merges to the main branch, ArgoCD automatically deploys it. And yes I've found ArgoCD removes most objects when they are deleted from Git.