How to convert json to a helm chart values.yaml
- Step 1Export or compose the JSON configuration — Start from a Terraform variable JSON, a CI-generated config object, or manually compose the key-value structure that matches your Helm chart's values schema.
- Step 2Convert to YAML — Paste the JSON and click Convert. The output is a YAML values file with nested keys for image.repository, service.port, ingress.enabled, and other standard chart value patterns.
- Step 3Validate against the chart's values.schema.json — Many production Helm charts include a values.schema.json. Convert the generated YAML back to JSON and run it through a JSON Schema validator to catch missing required values before helm upgrade.
- Step 4Commit or pass to helm install — Save as values-production.yaml and commit to your GitOps repo, or pass directly to Helm: helm upgrade my-release my-chart --values values-production.yaml.
Frequently asked questions
How do I handle values that Helm expects as strings but JSON stores as numbers?+
Some Helm charts expect port numbers or version strings as YAML strings (e.g. '8080' quoted) rather than integers. The converter follows standard JSON type mapping, so numbers become unquoted YAML integers. If a specific value needs to be a YAML string, add quotes manually in the output file.
Can I merge multiple JSON configs into one values.yaml?+
Convert each JSON file separately, then use the JSON Object Merger tool to merge them before converting to YAML. Alternatively, Helm supports multiple --values flags — you can keep per-environment overrides as separate YAML files and let Helm merge them at deploy time.
Is the chart configuration transmitted to JAD Apps?+
No. Conversion runs entirely in your browser using js-yaml. Image registry credentials, TLS secret names, and cluster-specific configuration are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.