A K3s cluster running on 2 Proxmox hosts went down completely after a few seconds of network interruption: both the host and the etcd quorum were taken out together. Here's why Corosync's self-fencing was the real cause, and how node placement design prevents it.
How long does failover really take with K3s embedded etcd versus kubeadm stacked/external etcd? We examine the gap between official RTO targets and real-world recovery times, and how failure domains and node counts differ.
K3s's etcd snapshots looked healthy every day, yet restore failed during a real outage. Three real-world traps — token management, S3 restore incidents, and cluster-reset pitfalls — reveal what's really at risk in embedded etcd backups.
A deep dive into how live-migrating a K3s control plane VM on Proxmox can break etcd quorum, explained through heartbeat/election-timeout mechanics and Proxmox affinity design, with concrete operational countermeasures.