All Tools View Categories About Contact Privacy

Kubernetes YAML to Helm Converter

Turn a Kubernetes manifest into a Helm chart scaffold (values.yaml + templates).

Runs entirely in your browser - nothing is uploaded and no cluster connection is made.
Your generated Helm scaffold will appear here.

About Kubernetes YAML to Helm Converter

Helm charts keep configuration in values.yaml and templates. The Kubernetes YAML to Helm Converter takes a plain manifest and produces that scaffold: a values.yaml with the parameterized values and a template where each field becomes a {{ .Values.* }} reference, so you can lift an existing manifest into a reusable chart.

Paste one manifest or a multi-document file. By default apiVersion and kind stay static while names, images, replicas and every other scalar become values. Array items such as containers use (index ...) references that map exactly to the values file.

Everything runs locally and nothing is uploaded.

Features

  • values.yaml - parameterized values extracted.
  • Templates - {{ .Values.* }} references.
  • Arrays - (index .Values.* N).key for list items.
  • Multi-doc - namespaced resource0/resource1.
  • Static option - keep apiVersion/kind fixed.
  • Copy / Download / Print - get helm.txt wherever you need it.

How to Use

  1. Paste a Kubernetes manifest.
  2. Toggle apiVersion/kind static (default on).
  3. Watch the preview and export.

Examples

Example 1 - Deployment. metadata.name and image become values.

Example 2 - multi-doc. Deployment + Service namespaced.

Example 3 - arrays. containers[0].image referenced via index.

Benefits

  • Chart-ready - drop into a Helm chart.
  • Valid references - paths match values.yaml.
  • Flexible - choose what to parameterize.
  • Multi-doc - handles several resources.
  • Private - everything runs in the browser.
  • Copy, download or print - get the output where you need it.

Frequently Asked Questions

What does this converter produce?
It emits a Helm chart scaffold: a values.yaml holding the parameterized values and a templates/<kind>-<name>.yaml file where each chosen field is replaced by a {{ .Values.* }} expression.
Which fields are parameterized?
By default every scalar leaf is templated except apiVersion and kind, which stay static. You can choose to parameterize those too.
How are list items referenced?
Values inside arrays such as containers use (index .Values.spec.containers 0).image so the path maps exactly to the values file.
Does it handle multi-document YAML?
Yes. Each document becomes its own template; their values are namespaced under resource0, resource1 in a single values.yaml.
Does this connect to a cluster?
No. Everything is assembled in your browser and nothing is uploaded.
Can I download it?
Yes. Copy the output, download helm.txt, or print it.