devops/converter
Docker Compose to Kubernetes Manifest Converter - Free & Instant | Smocky
Compose → Kubernetes
A manifest for review
Nothing leaves your browser.
Environment values are emitted as plaintext ConfigMap data, not Secrets. Published host ports are omitted; generated Services use ClusterIP.
Generated manifest
Review before usePaste Compose YAML, then select Convert to generate Deployments, Services, and ConfigMaps.
Unsupported behavior appears in diagnostics and as comments in the YAML.
Frequently asked questions
Which Compose fields are converted?
Version one converts image, array-form command and entrypoint, environment values, individual ports and expose entries, and deploy.replicas. Other fields such as build details, volumes, healthchecks, networks, and resource limits are omitted with diagnostics.
Are environment values stored as Secrets?
No. Environment values are emitted as plaintext data in a Kubernetes ConfigMap and referenced by the Deployment. Review sensitive values and move them to a Secret yourself.
What happens to a published port such as 8080:80?
The manifest exposes container port 80 through a ClusterIP Service on port 80. Published host port 8080 is omitted and called out in diagnostics.
Can the converter resolve Compose variables or .env files?
No. Unresolved $VAR and ${VAR} values in converted fields stop conversion. The converter does not read .env files or the host environment.
Can I deploy the generated manifest as-is?
Treat it as a starting point for review, not a complete migration or evidence of runtime equivalence. Unsupported Compose behavior needs a manual Kubernetes design, and this tool does not contact a cluster or deploy resources.