Helm & Kustomize · Lesson 6 of 7 · 3 min read
Choosing and combining
Decision guide
- Third-party software → its official Helm chart, pinned version, values in Git, applied by Flux HelmRelease / Argo CD.
- Your services, few environments, simple differences → Kustomize base + overlays.
- Many similar services → one internal Helm chart with good defaults (or a Kustomize component library); each service has a values file/overlay.
- Need to tweak a chart without forking → Flux post-renderers or Kustomize
helmCharts+ patches. - Need hooks/rollbacks outside GitOps → Helm.
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.
Pitfalls to mention in interviews
- Template sprawl — charts with hundreds of
ifs are hard to review; keep charts opinionated and usevalues.schema.json. - Always
helm template/kustomize buildand diff in PRs — reviewers should see rendered YAML changes. - Pin chart versions;
latestor floating ranges in prod surprise you. - Immutable fields (selectors, Service
clusterIP, StatefulSetvolumeClaimTemplates) — changes need recreate/migration plans. commonLabelschanging selectors on existing Deployments breaks applies — uselabelswithincludeSelectors: false.- Helm CRDs aren't upgraded automatically.
- Drift: manual kubectl edits are overwritten by the next Helm upgrade or GitOps reconcile — by design.