excloud managed kubernetes / technical field guide

Two flows that make the control plane real

These explainers focus on the two moments that matter most in this codebase: cluster founding and node bootstrap. The first page explains how one operator request becomes durable cluster truth. The second explains how one VM proves identity and receives a topology-aware bundle it can actually execute.

Readability first

Light, high-contrast typography, narrower line lengths, and responsive section navigation for phones, tablets, and desktop.

Why and how

Each page explains not only the order of operations, but the first-principles reason that order exists.

Code-grounded

The content tracks the current handlers and repository layer, not an imagined future architecture.

Read Order

Start with founding, then move to execution

Explainer 01

POST /clusters

Why the API must create shared trust, control-plane machines, node rows, and future bootstrap identity before any VM can become Kubernetes.

Focus: transaction boundaries, cluster PKI, VM creation, node certs, DNS semantics, and why the request contract is shaped the way it is.

Explainer 02

GET /bootstrap/control-plane/:vm_id

Why bootstrap is rendered on demand, how the VM proves identity, and how durable cluster truth becomes local files and running services.

Focus: IMDS-backed auth, runtime certificate issuance, bundle anatomy, the full template map, and the handoff from API response to VM-side execution.