Opscraft
Helm & Kustomize · Lesson 7 of 7 · 3 min read

Interview questions and model answers

"Helm vs Kustomize — when do you use which?"

Helm is a templating and packaging tool with release tracking, rollbacks and hooks — ideal for distributing reusable applications and installing third-party software. Kustomize is template-free patching of plain YAML with bases and overlays — ideal for environment differences of our own services. In my setup Flux applies both: HelmReleases for third-party components like cert-manager and External Secrets, Kustomize overlays for our microservices, with post-renderers when we need to patch a chart.

"Explain Helm values precedence."

Chart values.yaml lowest, then parent-chart values for subcharts, then -f files in order with later ones winning, then --set flags highest. Maps deep-merge but lists are replaced entirely. I keep all values in Git and avoid --reuse-values so a deploy is fully described by its files.

"An upgrade failed and Helm says another operation is in progress."

The release is stuck in a pending state from an interrupted upgrade. I check helm history, roll back to the last deployed revision, and if that doesn't work remove the pending release secret for that revision. To prevent it, CI uses --atomic with a timeout and avoids concurrent deploys of the same release.

"How do you make pods restart when a ConfigMap changes?"

With Helm, a checksum annotation on the pod template of the rendered ConfigMap; with Kustomize, configMapGenerator adds a content hash to the name and updates references, so the pod template changes and a rollout happens. Alternatives are a reloader controller or reading config dynamically.

"How do you manage secrets with Helm/Kustomize in GitOps?"

Never plain in Git. External Secrets Operator syncing from AWS Secrets Manager using IRSA is my default; SOPS-encrypted secrets decrypted by Flux with a KMS or age key also work; Sealed Secrets is another option.

"How do you test charts in CI?"

helm lint, render with helm template and validate with kubeconform against the target Kubernetes version, unit tests with helm-unittest, policy checks with Conftest or Kyverno CLI, chart-testing to install changed charts into a kind cluster, and helm diff output on the PR.

"What happens to CRDs in a chart's crds/ folder on upgrade?"

Nothing — Helm installs them on first install only and never upgrades or deletes them. Operators either manage CRDs separately, ship them as templates behind a flag, or rely on the GitOps tool to apply them.