Kustomize — Template-Free Kubernetes Manifest Customization

What it is

Kustomize lets you customize Kubernetes manifests through overlays and patches without using templates. Maintained by SIG CLI and built into kubectl since version 1.14, it provides a declarative way to manage environment-specific YAML across dev, staging, and production. You keep a base set of manifests and layer environment-specific modifications on top.

Kustomize targets platform engineers, SREs, and DevOps teams who manage Kubernetes deployments across multiple environments and want to avoid the complexity of Helm's templating language.

How it saves time or tokens

Kustomize eliminates template syntax from your Kubernetes manifests. Your base YAML is valid Kubernetes YAML at all times, making it readable and testable without rendering. Overlays compose cleanly: you add patches, change image tags, or modify resource limits per environment without duplicating entire manifests. Since it is built into kubectl, there is no extra binary to install or maintain.

How to use

1. Create a base directory with your Kubernetes manifests:

# base/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-server
spec:
  replicas: 1
  template:
    spec:
      containers:
      - name: api
        image: myapp:latest
        resources:
          limits:
            memory: 256Mi

1. Create a kustomization.yaml for the base:

# base/kustomization.yaml
resources:
- deployment.yaml
- service.yaml

1. Create an overlay for production:

# overlays/production/kustomization.yaml
resources:
- ../../base
patches:
- patch: |-
    - op: replace
      path: /spec/replicas
      value: 3
  target:
    kind: Deployment
    name: api-server
images:
- name: myapp
  newTag: v2.1.0

1. Apply with kubectl:

kubectl apply -k ./overlays/production

Example

Preview the rendered output before applying:

kubectl kustomize ./overlays/production
# or standalone
kustomize build ./overlays/production

Related on TokRepo

• DevOps tools — infrastructure and deployment automation resources
• Featured workflows — curated developer resources across categories

Common pitfalls

• Deeply nested overlay structures become hard to reason about. Keep the overlay hierarchy to two levels (base + environment) for maintainability.
• Strategic merge patches silently ignore unknown fields. Validate your patches against the actual resource schema to catch errors early.
• Forgetting to list resources in kustomization.yaml means they are silently excluded from the build output.