Skip to main content

Kustomize Helper

by WebF1

Privacy First

Kustomization Builder

Kustomization Builder

Fill in the guided form to generate a clean kustomization.yaml. Add resources, namespace, namePrefix and nameSuffix, common labels and annotations, image overrides, configMap and secret generators, and patches. The YAML preview updates live and can be copied or downloaded. Everything runs locally in your browser.

Example output

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
metadata:
  name: demo-app
resources:
  - deployment.yaml
  - service.yaml
commonLabels:
  app: demo-app
images:
  - name: nginx
    newTag: "1.27"
Your input is processed locally in your browser and is never uploaded to WebF1.

Validation errors

  • name must not be empty.

Warnings

  • No resources listed. A kustomization.yaml usually references at least one resource.

Metadata

The kustomization name and optional namespace and name transforms.

Resources

File paths or globs referenced by this kustomization, one per line.

Common labels

Applied to all resources. Keys must be RFC 1123 labels.

Common annotations

Applied to all resources.

Images

Override image names, tags, or digests for all resources.

configMapGenerator

Generate ConfigMaps from literals, files, or env files.

secretGenerator

Generate Secrets from literals or files. Values are base64 encoded by kustomize.

Patches

Apply strategic merge or JSON patches to resources.

Generated kustomization.yaml

Live preview. Copy or download at any time.

# Generated by Kustomize Helper. Edit as needed.
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

Frequently asked questions

Is my kustomization.yaml uploaded anywhere?
No. The form state and the generated YAML live in your browser. No network request is made that contains your manifest content.
What fields are supported?
resources, namespace, namePrefix, nameSuffix, commonLabels, commonAnnotations, images (name, newName, newTag, digest), configMapGenerator, secretGenerator, and patches (strategic merge or JSON).
How are image overrides applied?
Each image entry lets you set newName, newTag, and digest. Kustomize rewrites container image references that match the name field across all resources.
Can I use inline patches instead of file paths?
Yes. Each patch entry accepts an inline patch body as well as a path. You can also mark a patch as JSON so kustomize applies it as a JSON patch instead of a strategic merge.
Does the builder validate names?
Yes. Names, namespace, namePrefix, nameSuffix, and label keys and values are checked against RFC 1123 and DNS subdomain rules. Problems are shown in the validation panel without blocking the preview.

Related tools

  • Manifest Inspector

    Paste or upload YAML and inspect multi-document manifests locally. Identifies kinds and warns about missing names, latest tags, and missing resource limits.

  • Overlay Generator

    Generate base and overlay (Dev, Staging, Prod) folder structures with a tree preview and per-environment YAML downloads.