Foundations
The stack, the two clusters, and the one object you declare
- Architecture Syself builds the whole cluster as one hash-pinned unit and locks it to a release before any node boots, so the boundaries between OS, topology, and cluster components are Syself's to manage, not yours.
- Management and Workload Clusters Your workload cluster is a complete Kubernetes cluster on your own Hetzner servers; the management cluster is where Syself runs the automation that builds and looks after it.
- Inside a Workload Cluster What a running workload cluster is made of: what sits on a control-plane node, what sits on a worker, how KubeGate fronts the API server, and how the pieces connect over the public internet.
- Cluster Stacks One version number pins the node OS, the cluster topology, and the cluster components together, so every cluster runs a combination Syself tested as a whole.
- Declarative Cluster Management Your whole cluster is one Kubernetes object, and Syself's controllers keep the running cluster matching it continuously, not just at apply time.