Skip to content

Commit e4805e3

Browse files
authored
Merge pull request #189946 from justindavies/autodrain
Add Node Autodrain
2 parents 155367f + e2d7f05 commit e4805e3

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

articles/aks/node-auto-repair.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,22 @@ Alternative remediations are investigated by AKS engineers if auto-repair is uns
4141
If AKS finds multiple unhealthy nodes during a health check, each node is repaired individually before another repair begins.
4242

4343

44+
## Node Autodrain
45+
[Scheduled Events][scheduled-events] can occur on the underlying virtual machines (VMs) in any of your node pools. For [spot node pools][spot-node-pools], scheduled events may cause a *preempt* node event for the node. Certain node events, such as *preempt*, cause AKS node autodrain to attempt a cordon and drain of the affected node, which allows for a graceful reschedule of any affected workloads on that node.
46+
47+
48+
The following table shows the node events, and the actions they cause for AKS node autodrain.
49+
50+
| Event | Description | Action |
51+
| --- | --- | --- |
52+
| Freeze | The VM is scheduled to pause for a few seconds. CPU and network connectivity may be suspended, but there is no impact on memory or open files | No action |
53+
| Reboot | The VM is scheduled for reboot. The VM's non-persistent memory is lost. | No action |
54+
| Redeploy | The VM is scheduled to move to another node. The VM's ephemeral disks are lost. | Cordon and drain |
55+
| Preempt | The spot VM is being deleted. The VM's ephemeral disks are lost. | Cordon and drain |
56+
| Terminate | The VM is scheduled to be deleted.| Cordon and drain |
57+
58+
59+
4460
## Limitations
4561

4662
In many cases, AKS can determine if a node is unhealthy and attempt to repair the issue, but there are cases where AKS either can't repair the issue or can't detect that there is an issue. For example, AKS can't detect issues if a node status is not being reported due to error in network configuration, or has failed to initially register as a healthy node.
@@ -50,7 +66,8 @@ In many cases, AKS can determine if a node is unhealthy and attempt to repair th
5066
Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.
5167

5268
<!-- LINKS - External -->
53-
5469
<!-- LINKS - Internal -->
5570
[availability-zones]: ./availability-zones.md
5671
[vm-updates]: ../virtual-machines/maintenance-and-updates.md
72+
[scheduled-events]: ../virtual-machines/linux/scheduled-events.md
73+
[spot-node-pools]: spot-node-pool.md

0 commit comments

Comments
 (0)