Helm values comparator
See exactly which chart values your override files change, add or remove, check the merged values against values.schema.json, and list template paths that are read but never set.
Up to 500,000 characters for values.yaml, 500,000 for override files (20 files), 200,000 for the schema and 500,000 for templates. Everything runs on your device in a background worker. Downloads: JSON report, CSV of changes and values.merged.yaml. Paste the default values.yaml of the chart. Up to 500,000 characters. Review the settings before running.
Your result
How to use Helm values comparator
- Paste the chart values.yaml.
- Paste your override files in -f order, separated by lines of three dashes.
- Optionally add values.schema.json and the chart templates.
- Run the comparison and download the report, CSV or merged values.
Useful next steps
How values are merged
Happytails.ai merges values the way helm install -f does, following the Helm docs page "Values Files" (helm.sh, read on 16 October 2026): later override files win, mappings merge key by key, lists and plain values are replaced, and null deletes a chart default. Keys that an override adds but the chart does not define are flagged, because they are often typos.
Schema and templates
When you paste values.schema.json, the merged values are validated with ajv, as Helm validates them before rendering (draft 7, 2019-09 and 2020-12; formats are not checked; only local $ref links are allowed). When you paste templates, every .Values path and index .Values call is listed so you can see paths that are read but not set and chart values that no template reads. Line numbers in override files and templates count from the top of their box.
Limits
Templates are scanned as text; Go template logic, include and tpl are not executed, so values read through variables are not seen. Subchart values, global values and --set flags are not applied.