Docker Compose to Kubernetes Converter
Convert Docker Compose YAML into Kubernetes Deployment, Service, and ConfigMap manifests with ports, env, volumes, and healthchecks mapped automatically in-browser.
Loading tool...
What is Docker Compose to Kubernetes Converter?
Docker Compose to Kubernetes Converter is a browser-based DevOps tool that parses docker-compose.yml files and generates starter Kubernetes manifests — a Deployment per service, an optional ClusterIP Service for exposed ports, and a ConfigMap for environment configuration — without uploading anything.
Key Benefits
- Skip the manual rewrite when migrating services from Compose to Kubernetes.
- Get best-practice manifests with labels, selectors, and multi-document YAML.
- See warnings for compose features that need human decisions, like build-only services.
- Keep internal compose files private because everything runs locally.
Common Use Cases
- •Bootstrap Kubernetes manifests from an existing docker-compose stack.
- •Learn the mapping between compose and Kubernetes concepts by example.
- •Prepare review-ready drafts for a Kompose-style migration workflow.
- •Generate starter manifests for demos and local clusters like minikube or k3d.
How to Convert Docker Compose to Kubernetes
- Paste compose file: Paste your docker-compose.yml into the input panel, or click Load sample to try one.
- Choose options: Set the target namespace, imagePullPolicy, and whether to generate Services and liveness probes.
- Convert: Click Convert to generate Deployment, ConfigMap, and Service manifests separated by ---.
- Copy or download: Review the warnings, then copy the YAML or download it as kubernetes-manifests.yaml.
Key Features
- Convert each compose service into a Deployment with labels and replicas.
- Generate ClusterIP Services with correct port and targetPort mappings.
- Move env_file and empty environment values into a generated ConfigMap.
- Translate healthchecks into liveness probes and honor deploy.replicas.
- Configure namespace and imagePullPolicy, then copy or download the YAML.
Frequently Asked Questions
What compose features are converted?
Services become Deployments with image, command, entrypoint, environment, ports, volumes, replicas, and restart policy mapped to their closest Kubernetes equivalents. Exposed ports can also generate a ClusterIP Service, and compose healthchecks translate into liveness probes.
What is NOT converted automatically?
Compose concepts without a direct equivalent are skipped or warned about: build contexts, depends_on ordering, host network mode, and secrets. The tool emits a warning for services that only have a build so you can set the image manually before deploying.
How are environment variables handled?
Named values with an equals sign become container env entries. Keys with empty values or env_file references move into a generated ConfigMap referenced through envFrom, which is the pattern Kubernetes recommends for non-secret configuration.
Does my compose file get uploaded anywhere?
No. Parsing and conversion happen entirely in your browser with JavaScript. Nothing is sent to a server, so internal or proprietary compose files never leave your machine.