Don't like ads? Go Ad-Free Today 

Kustomize kustomization.yaml Generator

DataDeveloper

ADVERTISEMENT · REMOVE?

INPUT

Auto Process

Resources

One resource path per line — local YAML files or directories/bases. Rendered under resources:.

Namespace

Optional. Sets namespace: for all resources (RFC 1123).

Name Prefix

Optional. Prepended to every resource name via namePrefix:.

Name Suffix

Optional. Appended to every resource name via nameSuffix:.

Common Labels

Optional. One key=value per line. Added to every resource via labels (includeSelectors).

Common Annotations

Optional. One key=value per line. Added under commonAnnotations:.

Image Overrides

Optional. One per line: matchName=newName:newTag. Use name=:tag for tag only, or name=@sha256:... for a digest. Rendered under images:.

Replicas

Optional. One per line: resourceName=count. Overrides replica counts via replicas:.

Generators

Add a configMapGenerator

ConfigMap Name

Base name (a content hash suffix is appended unless disabled).

ConfigMap Literals

One KEY=value per line. Added under the generator's literals:.

ConfigMap Files

Optional. One file path per line. Added under the generator's files:.

Disable content hash suffix (behavior: not_hashed)

Add a secretGenerator

Secret Name

Base name (a content hash suffix is appended unless disabled).

Secret Type

Sets the generator's type: field.

Secret Literals

One KEY=value per line (plain text — Kustomize base64-encodes at build time). Added under literals:.

Disable content hash suffix (behavior: not_hashed)

Patches

Optional. One patch file path per line. Rendered under the current patches: field (each as - path:).

OUTPUT

Client Side

ADVERTISEMENT · REMOVE?

Guide

Kustomize kustomization.yaml Generator

Assemble a valid kustomization.yaml file without memorizing the Kustomize schema. Pick the features you need — resources, name prefixes, labels, image overrides, generators, and patches — and the tool emits clean YAML using the current kustomize.config.k8s.io/v1beta1 API version, steering clear of deprecated fields that commonly slip into hand-written or AI-generated configs.

How to Use

List your resource files or bases, one path per line.
Optionally set a namespace, name prefix/suffix, common labels, and annotations.
Add image overrides as matchName=newName:newTag, or override replica counts.
Toggle a configMapGenerator or secretGenerator and supply literals or files.
Copy the generated kustomization.yaml or download it directly into your overlay directory.

Features

Current schema – Outputs apiVersion kustomize.config.k8s.io/v1beta1 with the modern labels and patches fields, not deprecated commonLabels or patchesStrategicMerge.
Resources & bases – Build the resources list from files or directory overlays.
Name transforms – Apply namespace, namePrefix, and nameSuffix across all resources.
Image overrides – Set newName, newTag, or a digest with registry-port-safe parsing.
Generators – Produce configMapGenerator and secretGenerator blocks, with optional content-hash suffix control.
Live validation – Inline warnings flag invalid RFC 1123 names, duplicate keys, and non-integer replica counts.

 FAQ

What is Kustomize and how does it differ from Helm?

Kustomize is a template-free way to customize Kubernetes manifests. Instead of using a templating language with placeholders like Helm, it layers declarative overlays on top of plain YAML base resources. It is built directly into kubectl via the -k flag, so no extra tooling is required.
Why does Kustomize add a hash suffix to generated ConfigMaps and Secrets?

By default, configMapGenerator and secretGenerator append a content-based hash to the resource name. When the contents change, the name changes, which forces Deployments that reference them to perform a rolling update. This guarantees pods pick up new configuration instead of silently keeping stale values.
What is the difference between namePrefix, commonLabels, and the labels field?

namePrefix and nameSuffix modify the metadata.name of every resource. The newer labels field adds key/value labels and can optionally include them in selectors via includeSelectors, whereas the deprecated commonLabels always injected into selectors, which could break existing Deployments whose selectors are immutable.
Why are some Kustomize fields like patchesStrategicMerge considered deprecated?

Older Kustomize versions used separate patchesStrategicMerge and patchesJson6902 fields. These were unified into a single patches field that accepts both strategic-merge and JSON 6902 patches with an optional target selector. Using the current schema avoids deprecation warnings and keeps files compatible with recent kubectl releases.