dekube¶
You deploy with Helm charts or helmfiles. Your users, your dev setup, or your NAS just need docker compose up. dekube generates compose.yml + reverse proxy config from your Kubernetes manifests — same charts, same values, no second stack to maintain.
Disclaimer: AI-generated code
This project was built by a human with AI as a typewriter. The architecture, design decisions, and scope creep are entirely human. The code was typed by Claude. Not entirely vibe-coded — but definitely not handwritten. For the full existential crisis, see About.
Sloppiness has been actively fought (or at least, I'm trying to).
If you just want it to work and don't care why, kubernetes2simple will handle everything. If you want to understand what you're running and control what gets loaded, helmfile2compose is the distribution for you. If you're here, you want to understand the engine itself, write extensions, or build your own distribution.
And lo, the architect who sought to render the celestial rites in common tongue found himself building a second heaven. "I have translated," he proclaimed, standing in a temple whose pillars bore the same glyphs as the first. The old gods smiled, for one does not carry fire without becoming a hearth.
— The Nameless City, On the Propagation of Temples (regrettably)
Understand dekube¶
How the conversion engine works — from concepts to internals.
- Concepts — design philosophy, emulation boundary, K8s vs Compose differences
- Architecture — converter pipeline, what gets converted, dispatch loop
- dekube-engine — the bare engine: package structure, three layers, pacts API
- Distributions — what a distribution is, how to build one,
_auto_register() - Build system — concatenation, import stripping,
sys.moduleshack
Extend dekube¶
Write extensions, maintain code quality, run the test suite.
- Code quality — linter scores, complexity metrics, existential dread
- Testing — regression suite, torture generator, performance tracking
- Writing extensions — converters, providers, transforms, rewriters, ingress providers
Reference¶
- CLI reference — command-line flags
- Configuration reference — full
dekube.yamlschema - Extension catalogue — the Eight Monks, third-party extensions, the full bestiary
- Pitfalls — null-safe YAML,
sys.modules, build system gotchas - Limitations — what gets lost in translation
- Roadmap — future plans (and past hubris)
- About — the complete and unhinged explanation
The ecosystem¶
| Repo | What it is |
|---|---|
| helmfile2compose | The distribution — core + 9 bundled extensions (Eight Monks + emptydir) → single helmfile2compose.py. |
| kubernetes2simple | Turnkey distribution — helmfile2compose + all extensions + automagic bootstrap. |
| dekube-engine | Bare conversion engine — empty registries, no opinions. Produces dekube.py. |
| dekube-manager | Package manager — downloads distribution + extensions, resolves dependencies. |
| Extensions | Single-file modules: providers, converters, transforms, rewriters. |
| dekube-testsuite | Regression suite + torture generator. |
License¶
Public domain; AI-typed, human insanity-designed.
Something broken? Open an issue on dekube-engine (engine/contracts), the relevant extension repo, or helmfile2compose (everything else — I'll triage).
Looking for the full record of what was done, and in what order? The cursed journal remembers.