Availability
- Keep workloads available How a node replacement moves your pods, the conditions every workload needs to survive it, and where to go next for your workload type.
- Keep stateless workloads available Apply the availability conditions to a stateless Deployment, size the PodDisruptionBudget and spread, and add the graceful shutdown that finishes in-flight requests through a node replacement.
- Keep ingress and load balancers available Keep your ingress controller and Hetzner load balancer serving through a node replacement with spread ingress replicas, a PodDisruptionBudget, and the right externalTrafficPolicy.
- Keep databases available How a database behaves when its node is replaced, why a single instance has a short gap, and how a replicated database with failover stays available.