- Docs
- Cluster management
Cluster management
Create and connect
- Create a cluster Define a cluster in the Cluster Configurator, apply the manifest to the management cluster, and watch Syself Autopilot provision it on Hetzner.
- Get the kubeconfig of a cluster Fetch the kubeconfig of a workload cluster from the management cluster, point kubectl at it, and confirm every node is Ready.
- Explore your cluster Run essential kubectl commands to inspect your Syself Autopilot cluster. Learn what healthy nodes, system pods, and events look like on a fresh cluster.
Configure the cluster
- Access a cluster through a domain Give the Kubernetes API server a stable domain name with a Hetzner Load Balancer and DNS, and understand how workload domains differ from the cluster endpoint.
- Configure OIDC Set up OIDC for Kubernetes cluster using token-based auth with your own identity provider and improve your operations.
- Encrypt etcd Turn on encryption at rest for Kubernetes Secrets so etcd never holds them in plaintext, and rotate the key when custody changes.
- Build an SCS-compatible cluster How to create a Kubernetes cluster compatible with the Sovereign Cloud Stack guidelines.
Manage from Git
- Introduction to GitOps Efficiently manage Kubernetes resources with GitOps tools for transparent, auditable, and automated deployment in modern cloud-native environments.
- Using Argo CD Learn how to set up Argo CD for managing Kubernetes resources, which goes hand in hand with deploying applications - following all GitOps best practices.
- Using Flux Learn how to set up Flux to manage your Syself Autopilot clusters from Git, including the remote management cluster target and the fields Syself Autopilot sets for you.
Lifecycle and upgrades
- Cluster lifecycle overview What you do across the lifecycle of a Syself Autopilot cluster, from keeping it healthy and backed up to updates, upgrades and node replacements, with links to each guide.
- Maintain a cluster Keep a Syself Autopilot cluster healthy. Check the control plane, the nodes and pending certificate requests manually or with alerts in your observability stack.
- Update cluster Update a cluster to a newer ClusterStack release on the same Kubernetes version — check your current release, edit the cluster object, and let the nodes roll.
- Upgrade Kubernetes version Move a running cluster to a new Kubernetes minor version — edit the cluster object, let the nodes roll, and confirm the upgrade finished.
- Migrate a manifest to v1beta2 Learn about the Cluster API v1beta2 update and how it affects your clusters.
Cluster workflows
- Run dev, staging, and prod Stand up separate clusters per environment and promote the same declaration through them.
- Throwaway clusters Spin up a short-lived cluster for a test, a demo, or a preview, then tear it down cleanly.
- Run a worker-less cluster Run a control-plane-only cluster for platform components, and know what stops working without workers.
- Delete a cluster Tear a cluster down in the safe order so nothing keeps billing and no data is lost by accident.
Troubleshooting
- Cluster creation fails Diagnose why your Syself Autopilot cluster is not coming up, from missing Hetzner secrets and quota limits to stuck machines.
- No servers available Resolve cluster degradation from Hetzner Cloud capacity limits. Move control planes and workers to bare-metal servers to avoid provisioning failures.
- Failed or stuck upgrades A stack or Kubernetes upgrade is not completing, so find what is blocking the rollout and how to recover.
- Control-plane and etcd recovery The API server is flapping or an etcd member is unhealthy, so restore quorum without making it worse.
- Expired certificates kubectl reports an expired certificate, so find out whether your kubeconfig or the API server certificate ran out, and renew the right one.