{"slug": "helm", "name": "Helm", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 3, "commenters": 14, "warners": 3, "score": 1.768, "rising": 0.35, "first": "2025-11-01", "latest": "2026-10-28", "why": "Helm is a great tool, but you absolutely must keep it simple.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 7, "compare": 1, "warn": 3}, "spark": [1, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1], "listed": true, "loved": [], "caveat": "", "short_quote": "Helm is a great tool, but you absolutely must keep it simple.", "icon": true, "domain": "artifacthub.io", "github_repo": null, "official_url": "https://helm.sh", "pricing": "", "aliases": ["Helm", "helm"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 802173920, "item_id": 50135870, "url": "https://news.ycombinator.com/item?id=50135870", "by": "bigstrat2003", "date": "2026-10-17", "stance": "recommend", "quote": "Helm is a great tool, but you absolutely must keep it simple.", "excerpt": "Helm is a great tool, but you absolutely must keep it simple. We use Helm at work, and our charts are 95% hard-coded YAML templates, with an occasional sprinkling of a Helm variable for values which differ between dev/test/prod. It works great and is a ton easier than Kustomize for that purpose. But I would never want to maintain the super complex Helm charts you see in public repos.", "context": "uses it at work", "use_case": "Kubernetes deployment templates", "switched_from": "", "story": "A skeptic's first contact with Kubernetes (2024)"}, {"id": 753321419, "item_id": 47082588, "url": "https://news.ycombinator.com/item?id=47082588", "by": "0xbadcafebee", "date": "2026-02-19", "stance": "recommend", "quote": "Helm is a perfectly acceptable way to quickly install K8s components", "excerpt": "Using GCP gives me the same feeling as vibe-coded source code. Technically works but deeply unsettling. Unless GCP is somehow saving you boatloads of cash, AWS is much better. RDS is a very quick way to expand your bill, followed by EC2, followed by S3. RDS for production is great, but you should avoid the bizarre HN trope of \"Postgres for everything\" with RDS. It makes your database unnecessarily larger which expand", "context": "", "use_case": "installing K8s components", "switched_from": "", "story": "Almost Every infrastructure decision I endorse or regret after 4 years"}, {"id": 734636720, "item_id": 45914795, "url": "https://news.ycombinator.com/item?id=45914795", "by": "vxvrs", "date": "2025-11-13", "stance": "recommend", "quote": "I don't feel like I'm running into any hurdles while using it", "excerpt": "As someone who stared out with Helm and has not used any of its alternatives, I had no idea how hated it is. Maybe it's just because of how I use it, but once I got the hang of the template charts I don't feel like I'm running into any hurdles while using it.", "context": "", "use_case": "Kubernetes package management", "switched_from": "", "story": "Helm 4.0"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 803405489, "item_id": 50212843, "url": "https://news.ycombinator.com/item?id=50212843", "by": "doctorpangloss", "date": "2026-10-23", "stance": "warn", "quote": "the lowest budget, flakiest and overbuilt alternative to plan manifests", "excerpt": "> We already run everything on Kubernetes, so deploying a service was mostly a matter of adding a Terraform module and a Helm chart. Haha \"we run everything on kubernetes, so deployment is a matter of using the least logical complement to it, and the lowest budget, flakiest and overbuilt alternative to plan manifests with none of the benefits of an operator\"", "context": "", "use_case": "deploying services", "switched_from": "", "story": "Can we replace a $150k Looker with a bucket of HTML files?"}, {"id": 802178112, "item_id": 50136132, "url": "https://news.ycombinator.com/item?id=50136132", "by": "baby_souffle", "date": "2026-10-17", "stance": "warn", "quote": "I can count all of the helm charts that didn't make me immediately want to cry with one hand", "excerpt": "> We use Helm at work, and our charts are 95% hard-coded YAML templates, with an occasional sprinkling of a Helm variable for values which differ between dev/test/prod. It works great and is a ton easier than Kustomize for that purpose. I have come to precisely the opposite conclusion. I can count all of the helm charts that didn't make me immediately want to cry with one hand... and I'd have at least 2 fingers still", "context": "", "use_case": "Kubernetes config", "switched_from": "", "story": "A skeptic's first contact with Kubernetes (2024)"}, {"id": 747322817, "item_id": 46707676, "url": "https://news.ycombinator.com/item?id=46707676", "by": "madduci", "date": "2026-01-21", "stance": "warn", "quote": "Helm Charts are a nice idea, but mistakes can happen really easy", "excerpt": "I use Terraform with the Kubernetes Provider, which is also actively developed by HashiCorp itself. Templating / injection of values has been much better, skipping the Helm Templating madness and relying on a set of tools that allow perform minting, security scans, generation of docs, unit tests and establish clear dependencies within Terraform, thanks to the graph model. Helm Charts are a nice idea, but mistakes can", "context": "", "use_case": "Kubernetes templating", "switched_from": "", "story": "Building Robust Helm Charts"}]}], "who": [{"by": "bigstrat2003", "context": "uses it at work", "url": "https://news.ycombinator.com/item?id=50135870", "date": "2026-10-17"}, {"by": "nullify88", "context": "runs a home lab", "url": "https://news.ycombinator.com/item?id=45913852", "date": "2025-11-13"}, {"by": "krowek", "context": "Long time vim/neovim user", "url": "https://news.ycombinator.com/item?id=45797867", "date": "2025-11-03"}], "tags": [], "use_cases": ["emacs completion", "deploying services", "kubernetes config", "kubernetes deployment templates", "deploying home services", "kubernetes deployments"], "compared": [{"slug": "vertico", "name": "Vertico", "co": 5, "switched_from": 0, "switched_to": 2}, {"slug": "terraform", "name": "Terraform", "co": 3, "switched_from": 0, "switched_to": 1}, {"slug": "orderless", "name": "Orderless", "co": 3, "switched_from": 0, "switched_to": 1}, {"slug": "corfu", "name": "corfu", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "consult", "name": "Consult", "co": 2, "switched_from": 0, "switched_to": 1}, {"slug": "kubernetes", "name": "Kubernetes", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "kustomize", "name": "Kustomize", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "eglot", "name": "Eglot", "co": 3, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=50273171", "title": "Emacs Turns 50", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=45783376", "title": "Ask HN: Where to begin with \"modern\" Emacs?", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=50127572", "title": "A skeptic's first contact with Kubernetes (2024)", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=45902604", "title": "Helm 4.0", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50212320", "title": "Can we replace a $150k Looker with a bucket of HTML files?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=50109715", "title": "What I self-host", "mentions": 1}], "sentiment_by_month": {"2025-11": {"compare": 1, "neutral": 3, "recommend": 1}, "2025-12": {}, "2026-01": {"warn": 1}, "2026-02": {"recommend": 1}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {"neutral": 1}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {"neutral": 3, "recommend": 1, "warn": 2}}, "quotes": [{"id": 804437156, "item_id": 50277322, "url": "https://news.ycombinator.com/item?id=50277322", "by": "seanw444", "date": "2026-10-28", "stance": "neutral", "quote": "I was using Helm, lsp-mode, yasnippet, and the like for a long time.", "excerpt": "I was using Helm, lsp-mode, yasnippet, and the like for a long time. I switched to Eglot/Corfu/Vertico/Tempel. I much prefer the new wave.", "context": "", "use_case": "Emacs completion", "switched_from": "", "story": "Emacs Turns 50"}, {"id": 804413524, "item_id": 50275845, "url": "https://news.ycombinator.com/item?id=50275845", "by": "cyrialize", "date": "2026-10-28", "stance": "compare", "quote": "Helm and Ivy are fully featured (I always forget how much Helm has for you).", "excerpt": "This is a good point, but I do want to mention that I feel like in the past 5 years we've had lots of extremely popular packages that hook into Emacs internals instead of rolling out their own architecture. For example, corfu [0] versus company [1]. Company works with capf, but you can also write your own backends for it (specific to company). Corfu also works with capf, but all backends are capf functions instead of", "context": "Emacs user", "use_case": "Emacs completion", "switched_from": "", "story": "Emacs Turns 50"}, {"id": 804385506, "item_id": 50274094, "url": "https://news.ycombinator.com/item?id=50274094", "by": "cyrialize", "date": "2026-10-28", "stance": "neutral", "quote": "I no longer use Helm (I'm doing Vertico/Orderless/Consult)", "excerpt": "About 10+ years ago I found a guide on Helm [0] and a guide on Org-mode [1] when I was just getting into Emacs. This helped me move on from using Spacemacs to making my own configuration. I no longer use Helm (I'm doing Vertico/Orderless/Consult), but I've stuck with Org-mode since then. I sometimes venture out to other apps (like Joplin, Obsidian, Apple Notes, Apple Reminders, etc), but Org-mode just works best for ", "context": "", "use_case": "Emacs completion", "switched_from": "", "story": "Emacs Turns 50"}, {"id": 803405489, "item_id": 50212843, "url": "https://news.ycombinator.com/item?id=50212843", "by": "doctorpangloss", "date": "2026-10-23", "stance": "warn", "quote": "the lowest budget, flakiest and overbuilt alternative to plan manifests", "excerpt": "> We already run everything on Kubernetes, so deploying a service was mostly a matter of adding a Terraform module and a Helm chart. Haha \"we run everything on kubernetes, so deployment is a matter of using the least logical complement to it, and the lowest budget, flakiest and overbuilt alternative to plan manifests with none of the benefits of an operator\"", "context": "", "use_case": "deploying services", "switched_from": "", "story": "Can we replace a $150k Looker with a bucket of HTML files?"}, {"id": 802178112, "item_id": 50136132, "url": "https://news.ycombinator.com/item?id=50136132", "by": "baby_souffle", "date": "2026-10-17", "stance": "warn", "quote": "I can count all of the helm charts that didn't make me immediately want to cry with one hand", "excerpt": "> We use Helm at work, and our charts are 95% hard-coded YAML templates, with an occasional sprinkling of a Helm variable for values which differ between dev/test/prod. It works great and is a ton easier than Kustomize for that purpose. I have come to precisely the opposite conclusion. I can count all of the helm charts that didn't make me immediately want to cry with one hand... and I'd have at least 2 fingers still", "context": "", "use_case": "Kubernetes config", "switched_from": "", "story": "A skeptic's first contact with Kubernetes (2024)"}, {"id": 802173920, "item_id": 50135870, "url": "https://news.ycombinator.com/item?id=50135870", "by": "bigstrat2003", "date": "2026-10-17", "stance": "recommend", "quote": "Helm is a great tool, but you absolutely must keep it simple.", "excerpt": "Helm is a great tool, but you absolutely must keep it simple. We use Helm at work, and our charts are 95% hard-coded YAML templates, with an occasional sprinkling of a Helm variable for values which differ between dev/test/prod. It works great and is a ton easier than Kustomize for that purpose. But I would never want to maintain the super complex Helm charts you see in public repos.", "context": "uses it at work", "use_case": "Kubernetes deployment templates", "switched_from": "", "story": "A skeptic's first contact with Kubernetes (2024)"}, {"id": 801950273, "item_id": 50121892, "url": "https://news.ycombinator.com/item?id=50121892", "by": "steezeburger", "date": "2026-10-16", "stance": "neutral", "quote": "", "excerpt": "I'm sure you could achieve almost all the things I needed with docker compose, but I was using it at work and had designed some clean helm charts so just used them at home. I use it when I need to deploy a service across multiple machines. For personal projects that's pretty much my biggest decider. Otherwise I'm using the same docker compose setup I've been using for a while!", "context": "", "use_case": "deploying home services", "switched_from": "", "story": "What I self-host"}, {"id": 776906881, "item_id": 48556680, "url": "https://news.ycombinator.com/item?id=48556680", "by": "JohnMakin", "date": "2026-06-16", "stance": "neutral", "quote": "The charts break terraform quite a bit sometimes, so you have to keep it simple", "excerpt": "Yea, I used to believe this too, and still sort of agree - I got so tired of the argument in maintaining k8s infra in terraform I gave up and wrote what is essentially a terraform wrapper module around helm. The charts break terraform quite a bit sometimes, so you have to keep it simple, and god help you if you want to use CRD's, hashicorp providers have the notion no one actually needs those. I had dismal hopes of i", "context": "", "use_case": "Kubernetes deployments", "switched_from": "", "story": "What job interviews taught me about Kubernetes"}, {"id": 753321419, "item_id": 47082588, "url": "https://news.ycombinator.com/item?id=47082588", "by": "0xbadcafebee", "date": "2026-02-19", "stance": "recommend", "quote": "Helm is a perfectly acceptable way to quickly install K8s components", "excerpt": "Using GCP gives me the same feeling as vibe-coded source code. Technically works but deeply unsettling. Unless GCP is somehow saving you boatloads of cash, AWS is much better. RDS is a very quick way to expand your bill, followed by EC2, followed by S3. RDS for production is great, but you should avoid the bizarre HN trope of \"Postgres for everything\" with RDS. It makes your database unnecessarily larger which expand", "context": "", "use_case": "installing K8s components", "switched_from": "", "story": "Almost Every infrastructure decision I endorse or regret after 4 years"}, {"id": 747322817, "item_id": 46707676, "url": "https://news.ycombinator.com/item?id=46707676", "by": "madduci", "date": "2026-01-21", "stance": "warn", "quote": "Helm Charts are a nice idea, but mistakes can happen really easy", "excerpt": "I use Terraform with the Kubernetes Provider, which is also actively developed by HashiCorp itself. Templating / injection of values has been much better, skipping the Helm Templating madness and relying on a set of tools that allow perform minting, security scans, generation of docs, unit tests and establish clear dependencies within Terraform, thanks to the graph model. Helm Charts are a nice idea, but mistakes can", "context": "", "use_case": "Kubernetes templating", "switched_from": "", "story": "Building Robust Helm Charts"}, {"id": 734636720, "item_id": 45914795, "url": "https://news.ycombinator.com/item?id=45914795", "by": "vxvrs", "date": "2025-11-13", "stance": "recommend", "quote": "I don't feel like I'm running into any hurdles while using it", "excerpt": "As someone who stared out with Helm and has not used any of its alternatives, I had no idea how hated it is. Maybe it's just because of how I use it, but once I got the hang of the template charts I don't feel like I'm running into any hurdles while using it.", "context": "", "use_case": "Kubernetes package management", "switched_from": "", "story": "Helm 4.0"}, {"id": 734621632, "item_id": 45913852, "url": "https://news.ycombinator.com/item?id=45913852", "by": "nullify88", "date": "2025-11-13", "stance": "neutral", "quote": "If I need to run some software now, I `helm template` the resources and commit those to git.", "excerpt": "Running my home lab at home, I've grown sick of constant Renovate PRs against the helm charts in use. I recall one \"minor\" update not long ago recently in CoreDNS was messing with the exposed ports in the service and installs broke for a lot of folks. If I need to run some software now, I `helm template` the resources and commit those to git. I'm so tired of some random \"Extended helm chart to customise labels / anno", "context": "runs a home lab", "use_case": "templating Kubernetes manifests", "switched_from": "", "story": "Helm 4.0"}, {"id": 732765875, "item_id": 45797867, "url": "https://news.ycombinator.com/item?id=45797867", "by": "krowek", "date": "2025-11-03", "stance": "neutral", "quote": "project.el, eglot, LSP things, helm, corfu, vterm, flycheck", "excerpt": "I was in the same boat until a couple of months ago. Long time vim/neovim user, used fennel to configure it lastly, but I wanted to see what Emacs has to offer to compare. I started by reading Mastering Emacs by Mickey Petersen and from there start adding things that I felt I needed (configure key bindings, project.el, eglot, LSP things, helm, corfu, vterm, flycheck, etc) I still have things to do, but I'm not in a h", "context": "Long time vim/neovim user", "use_case": "Emacs completion", "switched_from": "", "story": "Ask HN: Where to begin with \"modern\" Emacs?"}, {"id": 732548647, "item_id": 45784290, "url": "https://news.ycombinator.com/item?id=45784290", "by": "foobarqux", "date": "2025-11-01", "stance": "neutral", "quote": "helm-swoop is nice.", "excerpt": "Don't use doom etc, just standard emacs, otherwise you won't have any understanding of what is happening and how to fix it. Here's a list of what I think is important, roughly more important to less: - corfu+marginalia+vertico+embark+orderless is the standard completion stack now - magit (maybe also see also the \"casual\" the transient front end for other modes) - avy - (fset 'yes-or-no-p 'y-or-n-p) ; 'Y' or 'N' inste", "context": "", "use_case": "Emacs searching", "switched_from": "", "story": "Ask HN: Where to begin with \"modern\" Emacs?"}, {"id": 732540583, "item_id": 45783786, "url": "https://news.ycombinator.com/item?id=45783786", "by": "mijoharas", "date": "2025-11-01", "stance": "compare", "quote": "It's an alternative to helm and ivy (I've used each before).", "excerpt": "I've been using emacs for a decade by now. I'd look into spacemacs (what I use). It's similar to doom, in that it makes some decisions for you, but you can very much have a customized experience. I for instance have a lot of \"stock\" sections, and other things that are very customized that I've made myself. Look into the \"layers\" (sets of packages that work together). I'd particularly recommend checking out the comple", "context": "", "use_case": "Emacs completion", "switched_from": "", "story": "Ask HN: Where to begin with \"modern\" Emacs?"}]}