[{"data":1,"prerenderedAt":38},["ShallowReactive",2],{"blog-tag-en-etcd":3},[4,16,23,31],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\u002Fblog\u002Fen\u002Fproxmox-corosync-self-fencing-k3s-etcd-quorum","A K3s Cluster Built on 2 Proxmox Hosts Went Down Entirely After a Brief Network Blip. The Culprit Was Corosync's Self-Fencing","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.","2026-11-11",[10,11,12,13,14,15],"k3s","kubernetes","proxmox","etcd","high-availability","quorum",{"path":17,"title":18,"description":19,"date":20,"tags":21},"\u002Fblog\u002Fen\u002Fk3s-kubeadm-ha-etcd-failover-rto-gap","Your RTO Said 30 Seconds. It Took 3 Minutes. Why K3s and kubeadm HA Specs Don't Match Reality","How long does failover really take with K3s embedded etcd versus kubeadm stacked\u002Fexternal etcd? We examine the gap between official RTO targets and real-world recovery times, and how failure domains and node counts differ.","2026-10-09",[10,11,13,14,22],"kubeadm",{"path":24,"title":25,"description":26,"date":27,"tags":28},"\u002Fblog\u002Fen\u002Fk3s-etcd-snapshot-restore-token-cluster-reset-pitfalls","The Automated etcd Snapshots Were Running Every Day. Here's Why K3s Restore Still Failed in Production","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.","2026-09-21",[10,11,13,29,30,14],"backup-restore","disaster-recovery",{"path":32,"title":33,"description":34,"date":35,"tags":36},"\u002Fblog\u002Fen\u002Fk3s-proxmox-live-migration-etcd-quorum-affinity-design","Proxmox Live Migration Quietly Breaks K3s etcd Quorum: When Virtualization Collides with Raft","A deep dive into how live-migrating a K3s control plane VM on Proxmox can break etcd quorum, explained through heartbeat\u002Felection-timeout mechanics and Proxmox affinity design, with concrete operational countermeasures.","2026-09-09",[10,11,12,13,37,14],"live-migration",1794902589137]