Explain an existing values.yaml field by field in plain English, or build a clean one from scratch with a guided form. Nothing is ever uploaded — parsing happens locally with js-yaml.
Field-by-field breakdown
Generated values.yaml
Differences
How it works
The Explain tab parses your YAML with js-yaml and recursively flattens it into dot/bracket-notation paths, like image.repository or ingress.hosts[0].host, then matches each path against a regex-based glossary of common Helm chart conventions. The Diff tab flattens two documents the same way and compares every path present in either one to report what was added, removed, or changed.
FAQ
Why are some fields labeled as "custom value" instead of getting a real description?
The glossary only recognizes common Helm chart conventions, like image.repository or resources.limits.cpu, using pattern matching — any field name it doesn't recognize is assumed to be specific to that particular chart's own templates, since there's no universal standard for every possible values.yaml key.
How does the Diff tab handle a field that only exists in one of the two files?
It's flagged as added (present in B but not A) or removed (present in A but not B) rather than compared as a value change — the diff works by flattening both YAML documents into the same dot-notation paths and checking which paths appear in which file.
Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.