Graceful Degradation in Kubernetes: What Happens When Components Fail
What happens when Kubernetes components fail? Understand how kube-apiserver, etcd, scheduler, and kubelet failures affect your cluster.
From what a container actually is to running a cluster with no internet, with the failure modes that bite in between.
Nine posts, and the longest path on the site. It starts by separating simulation, emulation, virtualisation and containers, because most Kubernetes confusion is really confusion about one of those. Then the question of whether you need a cluster at all, then sizing, then the spine: etcd, graceful degradation, what unbreakable actually costs, chaos engineering, and finally a cluster that runs offline at the edge.
Start here if you have heard of Kubernetes and nothing else. By the end you will know which parts fall over first and what that looks like at 2am.
What happens when Kubernetes components fail? Understand how kube-apiserver, etcd, scheduler, and kubelet failures affect your cluster.
Why I'm obsessed with systems that keep working, even when they're broken.
Learn chaos engineering for Kubernetes. Intentionally break things to discover weaknesses before they become outages. Practical guide with Litmus Chaos.
How to run Kubernetes clusters in air-gapped and offline environments. Island mode architecture for edge computing, ships, and sovereign infrastructure.