// the find
arttor/helmify
Creates Helm chart from Kubernetes yaml
Helmify converts Kubernetes YAML manifests into Helm charts via stdin pipe or filesystem input. It's primarily aimed at operator-sdk/Kubebuilder projects where you want to ship your operator as a Helm chart without hand-writing all the templating. Works well as a `kustomize build | helmify` step in a Makefile.
The kustomize pipeline integration is the real use case here and it works cleanly — `kustomize build config/default | helmify chart` is genuinely useful for operator projects. Processor architecture is well-structured: each k8s resource type gets its own package implementing a common interface, so adding support for new types is straightforward. The e2e test actually runs `helm lint --strict` on the output, which catches real generation bugs rather than just asserting on YAML structure. cert-manager subchart support and CRD directory placement flags show awareness of real deployment constraints.
Manual edits to generated templates are silently overwritten on every run — there's no merge strategy or escape hatch, so you can't use this in a workflow where humans and helmify both touch the templates. Incremental adoption is basically impossible; you get a full regeneration or nothing. Support for newer Kubernetes resource types is patchy — no Gateway API, no HorizontalPodAutoscaler, no NetworkPolicy. The generated values.yaml is mechanical: every field gets exposed as a value, including ones nobody would ever override, producing charts that are hard to reason about compared to hand-crafted ones.