Project sources
- Helm pain points describes the project's fifteen operational problem areas.
- Configuration question workflow turns those areas into decisions a user can ask about one exact configuration.
- The internal planning material under
~/Desktop/HELMadds sceptical-user, serverless, Catalog-maintainer, GitOps, and fleet-operator perspectives.
Repeated public reports
| User problem | Representative reports |
|---|---|
| A chart upgrade combines old and new values in an unexpected way. | Helm #3957, cert-manager #7352 |
| An interrupted or failed upgrade leaves the release stuck. | Helm #8987, Helm #10599 |
| An existing Secret is configured, but an upgrade still asks for a password or fails authentication. | Bitnami PostgreSQL #24290, Grafana charts #3790 |
| A small chart change reaches immutable fields or persistent storage. | Grafana charts #1256, Grafana charts #1184 |
| CRD versions, ownership, and install order do not follow the ordinary workload path. | Prometheus Community charts #2921, Argo CD #20124 |
| GitOps changes Helm's hook, ordering, values, drift, or OCI behavior. | Argo CD #11074, Flux helm-controller #300, Flux discussion #1085 |
| Values and templates become hard to read, test, or customize without a fork or another overlay system. | Reddit: Helm or Kustomize, Reddit: tools people do not trust |
| Rollback does not reverse database migrations or other state outside Kubernetes objects. | Reddit: Helm rollback strategy |
What the reports change in the product
The first question should not be "which feature do you want?" It should be the decision the user is trying to make:
- What did these values change?
- What could break in this upgrade?
- What must exist before installation?
- Can I avoid a chart fork?
- Who runs the hooks and installs the CRDs?
- Can I return to the exact prior objects?
- How does this differ from what runs now?
- Which environments or clusters are affected?
Each answer must name the source and inputs, show exact objects, separate desired configuration from live state, state what was not checked, and end in one action. That action may remain local, produce OCI, become a public Catalog candidate, or save the reviewed result in ConfigHub.