In-place k3os upgrades versus CAPI-managed node replacement for etcd quorum safety
Maintaining etcd quorum across a k3os control plane during OS and k3s updates forces a choice between two documented paths: running k3os upgrade in place on each node and manually sequencing reboots, or adopting Cluster API (CAPI) to replace nodes immutably. The in-place approach is operationally simpler but risks quorum loss if multiple control-plane member