Skip to main content
Kustomize Helper

by WebF1

Overlay Generator

Overlay Generator

Define a base and toggle Dev, Staging, and Prod overlays. Set replicas, namespace, namePrefix, image tag overrides, and inline patches per environment. Preview the directory tree and download the generated YAML per file or all at once. Everything runs locally in your browser.

Example tree

my-app/
├── base/
│   ├── kustomization.yaml
│   ├── deployment.yaml
│   └── service.yaml
└── overlays/
    ├── dev/
    │   ├── kustomization.yaml
    │   └── dev-patch.yaml
    ├── staging/
    │   └── kustomization.yaml
    └── prod/
        ├── kustomization.yaml
        └── prod-patch.yaml
Your overlay spec is processed locally in your browser and is never uploaded to WebF1.

Base

Environments

Toggle environments to include in the overlay tree.

Directory tree

Fill in the application name and base details, or load the sample, to see the generated tree and YAML files here.

Private by design

Your YAML is parsed and processed entirely in your browser. Kustomize Helper does not upload imported manifest content, does not require an account, and does not use third-party tracking or advertising scripts. Read the full privacy page.

Frequently asked questions

Is my overlay spec uploaded anywhere?
No. The wizard state and generated YAML live in your browser. No network request is made that contains your configuration.
Which environments are supported?
Dev, Staging, and Prod. Toggle each environment on or off. Each environment can set replicas, namespace, namePrefix, an image tag override, and an inline strategic merge patch.
What does the output look like?
A base folder with kustomization.yaml, deployment.yaml, and service.yaml, plus an overlays folder with one subfolder per environment. Each overlay has its own kustomization.yaml and optional patch file.
Can I download all files at once?
Yes. The Download all button concatenates every generated file into a single YAML stream with path headers. You can also download each file individually.
Does the generator connect to a cluster?
No. It is a pure offline scaffolding tool. It does not run kubectl, does not apply manifests, and does not require credentials.

Related tools