Explain an existing kustomization.yaml field by field in plain English, or build one from scratch with a guided form. Nothing is ever uploaded — parsing happens locally with js-yaml.
Field-by-field breakdown
Generated kustomization.yaml
How it works
The Explain tab flattens the pasted kustomization.yaml into dotted/bracketed field paths (e.g. images[0].newTag) with js-yaml, then looks up each path against a built-in glossary of real Kustomize fields to show a plain-English description — anything not on that list is flagged as non-standard rather than guessed at; the Build tab does the reverse, assembling a kustomization.yaml line by line from form inputs like namePrefix, commonLabels, image overrides, and ConfigMap/Secret generator literals.
FAQ
Why does it say a field I copied straight from the Kustomize docs is "not a standard field"?
The glossary only matches field paths against a fixed set of regular expressions covering the documented top-level keys — a deeply nested or unusually-shaped path (or a genuine plugin/transformer-specific field) can fall through and get labeled non-standard even when it's valid.
Does the Build tab check that my inputs produce valid YAML?
No — it does basic quoting (wrapping values that aren't simple bareword-safe strings in quotes) but doesn't validate the result against Kustomize's schema, so it's still worth running kustomize build locally before committing.
Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.