Kubernetes to docker compose. One command. Too simple.
Python 3.10+ and Docker required. That's all.
compose.yml. Everything it installed lives in
.kubernetes2simple/ — your system stays clean.
Yes, any time. compose.yml and Caddyfile
are regenerated on every run. To customize something, edit
helmfile2compose.yaml instead — that file is yours.
If your project uses cert-manager, self-signed certificates are generated locally so things can start. Fine for development — not for production.
CronJobs, resource limits, probes, HPA — anything without a compose equivalent is skipped with a warning. The goal is a working local environment, not a cluster replica.
Pass --env <name> to select one. Pick the environment
closest to dev or demo.
Open an issue. Describe what you pointed it at, paste the output.
No. K2s (uppercase K) is a Kubernetes distribution for Windows by Siemens Healthineers. k2s (lowercase) is this project. Different thing, similar name, no affiliation.
The script downloads the conversion engine and the extensions your
project needs, runs helmfile template (or reads your
manifests), and converts everything to a compose.yml +
reverse proxy config. The conversion is static — no agent, no
daemon, no controller. Run it again any time to regenerate.
dekube is the conversion engine behind this script — an extension system, a package manager, and documentation written as forbidden texts for a forbidden act. kubernetes2simple detects your project, picks the right extensions, and runs dekube for you. One command instead of understanding the architecture.