SPSai Piseyinsaipisey.hashnode.dev·19h ago · 2 min readOne command tells you if your next Kubernetes upgrade will brick a nodeSince v1.35, the kubelet setting failCgroupV1 defaults to true. On a node that still runs cgroup v1, the kubelet refuses to start, so the node goes NotReady and stays there. On a control-plane node it11V
SPSai Piseyinsaipisey.hashnode.dev·6d ago · 4 min readYour cluster says 3/3. It will still go dark with one zone.Every deployment in this three-zone cluster reports ready: $ kubectl get deployments NAME READY UP-TO-DATE AVAILABLE checkout-api 3/3 3 3 session-store 1/1 1 00
