World map

 

BM: Baca dalam Bahasa Melayu

World K4: Notes, Lockers & Packages

Helm or Kustomize?

You will learn: when to reach for Helm, when for Kustomize, and when for both.

Checked with Kubernetes 1.37 on 31 Oct 2026

The problem

You are here: cluster kind-dev namespace default
kubectl kustomize overlays/prod prints the prod YAML: a Namespace, the settings ConfigMap and a Deployment with 3 replicas. Terminal output: $ kubectl kustomize overlays/prod apiVersion: v1 kind: Namespace metadata: name: prod --- apiVersion: v1 data: GREETING: Selamat datang LOG_LEVEL: warn kind: ConfigMap metadata: name: settings namespace: prod --- apiVersion: apps/v1 kind: Deployment metadata: labels: app: shop name: shop namespace: prod spec: replicas: 3 selector: matchLabels: app: shop template: metadata: labels: app: shop spec: containers: - envFrom: - configMapRef: name: settings image: nginx:1.29-alpine name: web

Kustomize made prod’s YAML by patching plain files. Last lesson, Helm made YAML by filling holes. Two tools, one job? Your team is arguing.

Watch

Drag a card into a box. Or tap the card, then tap the box.

        Helm fills templates and remembers releases. Kustomize patches plain YAML, kitchen by kitchen. Many teams use both.

        Try it

        Make YAML both ways. First Kustomize’s dev kitchen, then Helm’s kit.

        You are here: cluster kind-dev namespace default
        Stalls: 3. Trays: 0 (0 ready). Waiting for a stall: 0.
        dev-control-planeOpenManager

        No trays here.

        dev-workerOpen

        No trays here.

        dev-worker2Open

        No trays here.

        Time: +0s (sped up)

        Predict

        You need a database that experts packaged, with 40 settings. Which do you reach for?

        Pick one answer.

        Check

        Which tool fits each job best?

        Drag a card into a box. Or tap the card, then tap the box.

            You did it!

            You can now choose between Helm and Kustomize for a job.

            Go deeper (optional)

            Using both is common. Render a chart with helm template, then patch it with an overlay. Kustomize can also render charts itself (helmCharts, with --enable-helm). The GitOps tools in World K7 understand both.

            Real rep (optional), on your own machine:

            Real mission

            1. helm template shop ./kedai > from-helm.yaml
            2. kubectl kustomize overlays/prod > from-kustomize.yaml

            0 of 3 steps done · Your ticks are saved.