Kustomize

Raised as a usability problem by 13 people on Hacker News over 8 years (2019–2026), in 12 threads.

People raised many different problems with Kustomize, but no single problem has yet been raised by 3 people in 3 different months and threads.

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 15 complaints

Couldn't understand how to use Kustomize despite a day of reading docs2026-10-18
Can't figure out how to do anything beyond the basic tutorials2025-11-12
Same resources must be patched separately for each environment, instead of setting one variable2024-08-08
Changing a simple setting like ingress URL requires finding and nesting resources everywhere2024-06-25
Docs lack concrete examples, making the model hard to learn2024-04-04
Too limited and opinionated, causing heavy duplication across many deployments2024-04-04
Finds Kustomize and Helm confusing to use and understand2024-01-24
JSON patches are unintuitive and need helper tooling to generate2023-12-15
Weird patch syntax and must read many files to see what's happening2023-12-14
Tutorials are unclear, making it hard to deploy one YAML copy to multiple environments2023-12-14
Changing one attribute means flipping between many layered files to find the right one2023-09-23
Overlay semantics are funky and unintuitive for engineers who use Kustomize infrequently2022-10-17
Kustomize documentation is poor and the tool is awkward to work with2020-01-30
User couldn't figure out how to write Job/CronJob configs with generators2020-01-10
Found Kustomize very difficult to use and overly verbose for their use case2019-01-30