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: articles/aks/node-auto-repair.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ kubectl get nodes
30
30
31
31
Auto-repair takes several steps to repair a broken node. If a node is determined to be unhealthy, AKS attemps several remediation steps. The steps are performed in this order:
32
32
33
-
1. After the Docker runtime becomes unresponsive for 10 minutes, Docker is restarted on the node.
33
+
1. After the container runtime becomes unresponsive for 10 minutes, the failing runtime daemons and related services are restarted on the node.
34
34
2. If the node does not become available withint 10 minutes, the node is rebooted.
35
35
3. If the node is not available within 30 minutes, the node is re-imaged.
0 commit comments