Products · Product
Helm
Raised as a usability problem by 78 people on Hacker News over 11 years (2016–2026), in 60 threads.
No issue was raised by at least 3 people in 3 threads this year.
- 1
- 2
- 3
- 4
- 1
- 2
- 3
- 4
- 5
Every issue, all time, most people first
Helm templates are hard to read compared to raw resource configsUnreviewed
20162026- Helm and dbt both use the same charts/ directory, causing confusing conflicts2026-09-15
- Helm templating is convoluted, with indent and multi-level string templating making charts hard to maintain2024-08-08
- Helm is described as terrible with no specific usability problem named2024-04-04
Helm makes simple YAML files complex and changes harder to makeUnreviewed
20162026- Templates on YAML break linting tools like yamllint, making configs hard to validate2025-11-12
- YAML/Helm template editors aren't indent-aware, making editing maddening2025-11-12
- Helm charts are miserable to edit; editors can't help with templated YAML files2024-01-23
Templates work at syntax level, making charts hard to operateUnreviewed
20162026- Can't relate application docs to chart options, must grep templates to configure2025-11-14
- Poorly documented charts force users to grep templates to find settings2025-11-12
- Default chart template has too many options and values for beginners2025-11-12
Whitespace-sensitive template operators are tedious and error-proneUnreviewed
20162026- Templating text is cumbersome and error-prone, with fragile indentation for values2025-06-19
- Must count spaces by hand to get indentation right in templates2025-03-28
- Templates need manual indentation filters like nindent, which the tool could handle itself2024-11-07
Cryptic error messages hid an indentation mistake, costing hoursUnreviewed
20162026- Cryptic error messages hid a two-space indentation mistake, costing hours of debugging2023-09-28
- Template error messages point to the wrong line, costing hours of debugging2023-06-25
- Typos produce errors far from the actual mistake, and wrong output is hard to debug2023-06-01
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Helm and dbt both use the same charts/ directory, causing confusing conflicts2026-09-15
- Too many separate tools are needed for planning, rollout tracking, logs and status2026-02-11
- Can't relate application docs to chart options, must grep templates to configure2025-11-14
- Must fork charts to add config overrides; debugging broken installs and upgrades is painful2025-11-13
- Templates on YAML break linting tools like yamllint, making configs hard to validate2025-11-12
- Consumers can't change anything the chart author didn't expose, forcing bloated configs2025-11-12
- Poorly documented charts force users to grep templates to find settings2025-11-12
- Default chart template has too many options and values for beginners2025-11-12
- YAML/Helm template editors aren't indent-aware, making editing maddening2025-11-12
- Whitespace-sensitive text templating causes errors only discovered after submitting to cluster2025-07-19
- Templating text is cumbersome and error-prone, with fragile indentation for values2025-06-19
- Go templates are hard to debug and produce gibberish error messages2025-06-19
- Unclear which values.yaml changes apply and which need startup; unsure which services are safe to restart2025-06-16
- Must count spaces by hand to get indentation right in templates2025-03-28
- New users get a convoluted maximal template when expecting a minimal starting point2025-01-11
- Templates need manual indentation filters like nindent, which the tool could handle itself2024-11-07
- Stray spaces or tabs silently break templates, and final output is often hidden from developers2024-11-07
- Helm templating is convoluted, with indent and multi-level string templating making charts hard to maintain2024-08-08
- Failed install leaves no top-level status, forcing manual digging and deletion of chart resources2024-08-01
- Programmatic chart templates hide intended state, so config can't be searched or understood without running it2024-06-26
- Can't predict which YAML gets applied after a top-level change2024-06-25
- Every chart uses its own arbitrary layout and naming for value fields2024-06-25
- Helm is described as terrible with no specific usability problem named2024-04-04
- Helm templating is string-based and obtuse, making complex deployments hard to write and package2024-04-04
- Must press Ctrl+Space explicitly to select, unlike ivy-avy's single-key selection2024-02-05
- Error messages are raw Go stack traces, hard to understand2024-01-23
- Helm charts are miserable to edit; editors can't help with templated YAML files2024-01-23
- Templates are text substitution rather than syntax-aware, making chart writing horrible2024-01-23
- Chart values files are incomplete, poorly documented and overwhelmingly long, so users must read source2023-12-15
- Easy to get values wrong silently, producing semantically valid but incorrect output2023-12-15
- Hard to get template configuration right, requiring endless trial and error2023-12-15
- Error messages when a deployment fails are obtuse and hard to act on2023-12-15
- Text-based templating and config languages are error-prone and hard to work with2023-12-15
- No way to disable a template, forcing manual edits or bash scripting workarounds2023-12-15
- Config options pass through layers of indirection, so changing settings or debugging is hard to follow2023-11-26
- Templates work at the syntax level, making charts unnecessarily hard to operate2023-10-19
- Cryptic error messages hid a two-space indentation mistake, costing hours of debugging2023-09-28
- Debugging complex Helm templates is a nightmare without good tooling2023-09-22
- Hardcoded indentation for each generated block makes templates hard to write and maintain2023-09-21
- Template error messages point to the wrong line, costing hours of debugging2023-06-25
- Typos produce errors far from the actual mistake, and wrong output is hard to debug2023-06-01
- Easy to break templates with misplaced whitespace-trim markers and must count spaces for nindent2022-11-13
- Navigation bar links lead to 404 pages, so visitors cannot learn what Helm is2022-11-01
- Helm charts lack needed parameters, forcing manual edits to generated manifests2022-10-17
- Helm hides components that should be visible, so operators misdiagnose issues2022-10-17
- Templating syntax like the indent function is error-prone and hard to maintain2022-08-09
- Chart files are endless repetitive boilerplate that authors must write2022-05-16
- Hard to follow how to write config; YAML array merging makes extra alerts awkward2022-05-14
- Templates too inflexible to update API versions without forking the whole chart2021-12-08
- Doing too many things leads engineers to make mistakes and makes debugging hard2021-11-17