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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,9 +34,9 @@ kubectl get nodes
34
34
35
35
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:
36
36
37
-
1. Docker is restarted on the node
38
-
2. The node is rebooted
39
-
3. The node is re-imaged
37
+
1. Docker is restarted on the node.
38
+
2. The node is rebooted.
39
+
3. The node is re-imaged.
40
40
41
41
> ![Note]
42
42
> If multiple nodes are unhealthy, they are repaired one by one
0 commit comments