GitHub user rafaelpagliari added a comment to the discussion: Upgrading K8s Cluster Failed
cloud@k8s-acs1-control-1985b69a62a:~$ kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-acs1-control-1985b69a62a Ready control-plane 52m v1.28.4 k8s-acs1-node-1985b6a1fae Ready <none> 52m v1.28.4 k8s-acs1-node-1985b6a92a2 Ready,SchedulingDisabled <none> 52m v1.27.3 k8s-acs1-node-1985b6b0fc4 Ready <none> 52m v1.27.3 It always updates control + node1, it no longer updates node2 and gives the unable to update. This is the scenario on my ACS1... It updated successfully on ACS2. They have the same k8s version and the same ACS version. GitHub link: https://github.com/apache/cloudstack/discussions/11006#discussioncomment-13936448 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
