@@ -6,7 +6,7 @@ ms.custom: troubleshooting
6
6
ms.topic : troubleshooting
7
7
ms.date : 06/25/2025
8
8
ms.author : jeremyhouser
9
- author : jeremyhouser
9
+ author : jeremyhouser-ms
10
10
---
11
11
# Troubleshoot a KubernetesCluster with a node in NotReady,Scheduling Disabled state
12
12
@@ -30,7 +30,7 @@ This procedure may be performed at any time after the issue occurs to quickly re
30
30
$ kubectl get nodes -o wide
31
31
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
32
32
example-naks-control-plane-tgmw8 Ready,SchedulingDisabled control-plane 2d6h v1.30.12 10.4.32.10 < none> Microsoft Azure Linux 3.0 6.6.85.1-2.azl3 containerd://2.0.0
33
- example-naks-agentpool1-md-s8vp4-xp98x Ready,SchedulingDisabled < none> 2d6h v1.30.12 10.4.32.11 < none> CBL-Mariner/Linux 6.6.85.1-2.azl3 containerd://2.0.0
33
+ example-naks-agentpool1-md-s8vp4-xp98x Ready,SchedulingDisabled < none> 2d6h v1.30.12 10.4.32.11 < none> Microsoft Azure Linux 3.0 6.6.85.1-2.azl3 containerd://2.0.0
34
34
~~~
35
35
36
36
1. Issue the kubectl command to uncordon the Node in the undesired state.
@@ -45,7 +45,7 @@ This procedure may be performed at any time after the issue occurs to quickly re
45
45
$ kubectl get nodes -o wide
46
46
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
47
47
example-naks-control-plane-tgmw8 Ready control-plane 2d6h v1.30.12 10.4.32.10 < none> Microsoft Azure Linux 3.0 6.6.85.1-2.azl3 containerd://2.0.0
48
- example-naks-agentpool1-md-s8vp4-xp98x Ready < none> 2d6h v1.30.12 10.4.32.11 < none> CBL-Mariner/Linux 6.6.85.1-2.azl3 containerd://2.0.0
48
+ example-naks-agentpool1-md-s8vp4-xp98x Ready < none> 2d6h v1.30.12 10.4.32.11 < none> Microsoft Azure Linux 3.0 6.6.85.1-2.azl3 containerd://2.0.0
49
49
~~~
50
50
51
51
If you still have questions, [contact support](https://portal.azure.com/? # blade/Microsoft_Azure_Support/HelpAndSupportBlade).
0 commit comments