Docker Compose to Helm Chart Converter
Turn the first service of a docker-compose.yml into a Helm chart with a Deployment, Service and values.yaml.
Loading Docker Compose to Helm Converter...
How to Convert Docker Compose to a Helm Chart
Input Your Docker Compose File
Start by providing your docker-compose.yml file. Whether you're packaging your application for Helm or migrating to Kubernetes:
Automatic Chart Generation
The converter builds a starter Helm chart from the first service in your compose file. A note above the output lists anything it could not carry over:
Review and Customize
Browse through the generated Helm chart files using the dropdown selector:
Deploy with Helm
Deploy your application to Kubernetes using Helm:
helm install myapp ./myapphelm upgrade myapp ./myapp to updateFrequently Asked Questions
Why convert Docker Compose to Helm charts?
Helm is the package manager for Kubernetes. A chart gives you versioned releases, rollbacks and one values file per environment, which Compose does not have. Starting from your existing docker-compose.yml saves you writing the Deployment and Service by hand.
What's included in the generated Helm chart?
Chart.yaml, values.yaml, and a templates/ folder with a Deployment, a Service (when the service publishes or exposes ports), a PersistentVolumeClaim (when it has volumes) and _helpers.tpl with the usual name and label helpers. The ZIP puts everything in a myapp/ folder, so helm install myapp ./myapp works right after unzipping.
Which parts of my compose file are carried over?
The image (registry ports, tags and digests included), deploy.replicas, every port in short or long form (host IPs are dropped, /udp is kept, small ranges are written out port by port), environment in list or map form, command and entrypoint, deploy.resources (memory like 512M becomes 512Mi) and the container path of the first volume. Anything that is left out, such as env_file, depends_on, healthcheck, ports written as ${PORT}, or variables taken from your shell, is listed in a note above the output.
Will my environment values change?
No. Values are copied as you typed them, so 8901240544102066246, 00501, 14.50, true or yes stay exactly that. In values.yaml every value is quoted, and the Deployment writes them with quote, because Kubernetes only accepts strings in an env value and Helm would otherwise read yes or 00501 as something else.
How do I deploy multiple services from Docker Compose?
Only the first service in the file is converted, and the note above the output names the ones that were left out. Convert each service on its own to get one chart per service, or copy the Deployment and Service templates inside one chart and give each a values section of its own.
Can I use the chart in production as is?
Treat it as a starting point. Check the resource limits (if your compose file sets none, the chart uses example values of 500m CPU and 512Mi memory), add health checks, an Ingress if you need one, and run helm lint and a test install before relying on it.
Is my compose file uploaded anywhere?
No. The chart is built in your browser, so the compose file you paste or upload, including any passwords in it, never leaves your computer.
Related Tools
Docker Compose to Kubernetes
Convert Docker Compose files to Kubernetes manifests with Deployments, Services, and PVCs
Kubernetes to Docker Compose
Convert Kubernetes manifests to Docker Compose format for local development
Kubernetes YAML Fixer
Fix broken Kubernetes manifests automatically, repair Deployment, Service, Pod, and ConfigMap YAML errors
Kubernetes to Helm Chart
Generate Helm charts from Kubernetes manifests with Chart.yaml, values.yaml, and templates
Helm to Kubernetes
Convert Helm charts to plain Kubernetes manifests by rendering templates with values
Kustomize to Helm
Convert Kustomize configurations to Helm charts with templates and values