You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/availability-performance/node-not-ready-then-recovers.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,7 @@ There are several scenarios that could cause a "Not Ready" state to occur:
24
24
25
25
## Resolution
26
26
27
-
Check the API server availability by running the `kubectl get apiservices` command.
28
-
29
-
Make sure that the readiness probe is correctly configured in the deployment YAML file.
27
+
Check the API server availability by running the `kubectl get apiservices` command. Make sure that the readiness probe is correctly configured in the deployment YAML file.
30
28
31
29
For further steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).
0 commit comments