Hosted Kubernetes API
Kubernetes clients can use API, YAML, CRD, and Helm-shaped views backed by Dodona resources rather than a second application model.
Kubernetes compatibility
Keep the ecosystem. Change the operating model when you are ready.
Kubernetes is mature, widely understood, and often the direct choice. Dodona treats its API and workload shapes as an optional compatibility and migration surface over the same underlying state.
Compatibility view
YAML and native objects converge on one source of truth.
Translated semantics
Scheduler behavior is translated from identified upstream Kubernetes source with provenance and upstream-derived fixtures.
Migration in either direction
Existing workloads can enter through familiar shapes while native services use Dodona names, identity, delegation, and audit directly.
Measured posture
408 selected conformance tests passed on one pinned local rig.
On 2026-07-13, the local two-node Dodona rig passed all 408 tests selected by the official Kubernetes v1.31.14 `[Conformance]` run, with no expected failures.
Exact scope
This is local pinned-version evidence. It is not CNCF certification, cloud-provider certification, or evidence for later Kubernetes minors. A smaller scripted hosted-apiserver compatibility gate also exists and is not a substitute for that official run.
Dodona and k3s solve different first problems.
| Question | k3s / Kubernetes | Dodona |
|---|---|---|
| Primary operating model | Kubernetes resources, controllers, pods, and cluster ecosystem. | Names, workload identity, delegated authority, execution, and audit. |
| Best direct fit | Teams that want Kubernetes’ mature operating model and ecosystem. | Teams that want identity-aware service and agent calls as the substrate. |
| Interoperability | The native platform. | Kubernetes is an optional API and workload compatibility view. |
This is a fit distinction, not a maturity, performance, or superiority claim. If Kubernetes is the goal, k3s is a direct and established choice.
Next step
Use compatibility as an offramp, not a new identity.
Evaluate whether your existing YAML can coexist with native Dodona naming, identity, policy, and audit.