So, I upgraded to rancher 2.4 to try the zero-down...
# general
e
So, I upgraded to rancher 2.4 to try the zero-downtime upgrade. Now one master has been stuck in cordoned-state since last night and cluster is stuck in “Currently updating”. The node says kubelet stopped posting node status. What to do? Can I abort the cluster upgrade somehow?