[{"data":1,"prerenderedAt":25},["ShallowReactive",2],{"blog-tag-en-kubeadm":3},[4,15],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\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,12,13,14],"k3s","kubernetes","etcd","high-availability","kubeadm",{"path":16,"title":17,"description":18,"date":19,"tags":20},"\u002Fblog\u002Fen\u002Fk3s-kubeadm-memory-benchmark-datastore-comparison","Is K3s Really Lighter? We Benchmarked It Against Standard Kubernetes (kubeadm), and the Results Were Split","Is K3s really as lightweight as everyone says? We compare K3s and kubeadm-based standard Kubernetes control plane memory and CPU usage using official data and multiple independent benchmarks, and explain why the datastore choice (etcd vs SQLite) can flip the result.","2026-10-04",[10,11,14,21,22,23,24],"resource-profiling","memory-benchmark","control-plane","datastore-comparison",1792592709714]