Migration
In development — not yet available
Migrating a cluster between hosted and self-hosted modes is not built yet. The hosted control plane is in early access, but there is no export/import migration flow between the two modes today — so ignore any older guide that walks you through one.
The idea
The hosted control plane is in early access; the migration flow between the two modes is not built yet. The intent is a no-lock-in promise you can actually exercise in both directions:
- Hosted → self-hosted — move a kubehz-run control plane onto your own Hetzner account and keep running.
- Self-hosted → hosted — hand an existing self-hosted control plane to kubehz and keep only workers on your account.
Your data stays yours throughout — that is the whole point of building on open source. We will document the real, tested steps here once the flow exists.
No lock-in today
Even without hosted migration, you are never locked in:
- lok8s is open source and provisions your cluster on your Hetzner account.
- The dashboard integration is opt-in and outbound-only; kubehz holds no inbound credentials to your cluster.
- Removing kubehz is one step —
lo kubehz deregisterunregisters the cluster, and deleting thekubehz-systemnamespace removes the in-cluster agent. Your cluster keeps running exactly as before.
Next steps
- Hosted control plane — the hosted path (early access)
- How it works — hosting × access, and your data
- KubeOne on Hetzner — provision on your own account today
Doc status
| Aspect | Detail |
|---|---|
| State | in development — not yet available |
| Last reviewed | 2026-07-10 |