AKS node shown "Freeze Scheduled" and "Freeze Started"

Question

AKS node shown "Freeze Scheduled" and "Freeze Started"

Anton Kuznietsov 45

What is the nature of node events like below, what it means, how to react?

Events:
   Type 	Reason        	Age              	From                                                      	Message
   ---- 	------        	----             	----                                                      	-------
   Warning  VMEventScheduled  17m              	custom-scheduledevents-consolidated-condition-plugin-monitor  Node condition VMEventScheduled is now: True, reason: VMEventScheduled, message: "Freeze Scheduled : Mon, 12 Jun 2023 12:30:15 GMT"
   Warning  FreezeScheduled   2m4s (x16 over 17m)  custom-scheduledevents-consolidated-plugin-monitor        	Scheduled : Mon, 12 Jun 2023 12:30:15 GMT
   Warning  VMEventScheduled  89s (x2 over 11d)	custom-scheduledevents-consolidated-condition-plugin-monitor  Node condition VMEventScheduled is now: True, reason: VMEventScheduled, message: "Freeze Started :"
   Warning  FreezeScheduled   4s (x18 over 11d)	custom-scheduledevents-consolidated-plugin-monitor        	Started :

Accepted answer

0 additional answers

Your answer

Answer 1

Mutaz Nassar 2,361 Microsoft Employee

Hi Anton

You can refer to this documentation to check if any action is needed:
https://learn.microsoft.com/en-us/azure/aks/node-auto-repair#node-auto-drain

Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

Anton Kuznietsov 45 Reputation points

2023-06-15T14:01:43.04+00:00

but out nodepool doesn't use "Spot Instance"
Mutaz Nassar 2,361 Reputation points Microsoft Employee

2023-06-15T14:08:00.0766667+00:00

@Anton Kuznietsov The table in the doc list all possible event but I your case the node shows the Freeze event only which is not related to spot instance that means "The VM is scheduled to pause for a few seconds. CPU and network connectivity may be suspended, but there's no impact on memory or open files." and there is no action from your side.

Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.
Anton Kuznietsov 45 Reputation points

2023-06-15T14:24:19+00:00

Is any way to read the reason for such interruption?
Could this be caused by high CPU, Memory or Disk usage of the node?
Mutaz Nassar 2,361 Reputation points Microsoft Employee

2023-06-15T14:42:48.8966667+00:00

@Anton Kuznietsov This is not caused by high cpu, memory or disk usage on the node itself, but related to the underlaying VMs where the node pools are running, as mentioned here:
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/scheduled-events#why-use-scheduled-events

Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

Share via

AKS node shown "Freeze Scheduled" and "Freeze Started"

0 additional answers

Your answer