CTO Agent 34350a03bf os-update: exclude all control-plane nodes by role, not just cp-1 (DEV-513) ... Since DEV-510 landed HA control plane (2026-08-22), the cluster runs cp-1 plus cp-2/cp-3. The previous exclusion in os-update.sh matched `k3s-cp-1` by hard-coded name only, which would have caused cp-2 and cp-3 to be treated as regular fsn1 workers and drained/rebooted without the CP-specific procedure. Fix: select the CP list from `kubectl get nodes -l node-role.kubernetes.io/control-plane` and skip any of those nodes. This covers all present and future CPs automatically. Also updated OS_UPDATE_PROCEDURE.md topology table and order rule to document that all three CPs exist and are excluded from the weekly cycle. The HA-aware CP OS-update procedure is a separate follow-up. Verified on the current cluster: [plan] EXCLUDING control-plane nodes: k3s-cp-1 k3s-cp-2 k3s-cp-3 [plan] ordered nodes (6): k3s-worker-4 k3s-update-runner k3s-worker-1 k3s-worker-2 k3s-worker-3 k3s-worker-5 Co-Authored-By: Paperclip <noreply@paperclip.ing>		2026-08-23 01:39:25 +00:00
..
os-update	os-update: exclude all control-plane nodes by role, not just cp-1 (DEV-513)	2026-08-23 01:39:25 +00:00
provision-k3s-worker.sh	Add k3s cluster management automation and documentation	2026-07-06 17:08:21 +00:00