IMDS query failed , exit code: 28

[ravinayag]

I have recently launched the AKS node pool with spot instances, The node get launched, I can see from the Kubectl get nodes in Ready Stattus.
However when i check with kubectl describe node i see some errors in the events. I thought it may be a random error. to check i deleted the node and autoscaler was able launch new node. But the erorrs on events still appeared on new node.

Can i continue this node with worloads ? what is the impact continuing with the errors.?
Any known issue or fix available?

  Type     Reason                   Age                From                                                          Message
  ----     ------                   ----               ----                                                          -------
  Normal   Starting                 55s                kube-proxy
  Normal   NodeHasSufficientMemory  73s (x2 over 73s)  kubelet                                                       Node aks-apppoolspot-31828581-vmss000001 status is now: NodeHasSufficientMemory
  Warning  InvalidDiskCapacity      73s                kubelet                                                       invalid capacity 0 on image filesystem
  Normal   NodeHasNoDiskPressure    73s (x2 over 73s)  kubelet                                                       Node aks-apppoolspot-31828581-vmss000001 status is now: NodeHasNoDiskPressure
  Normal   NodeHasSufficientPID     73s (x2 over 73s)  kubelet                                                       Node aks-apppoolspot-31828581-vmss000001 status is now: NodeHasSufficientPID
  Normal   NodeAllocatableEnforced  73s                kubelet                                                       Updated Node Allocatable limit across pods
  Normal   Starting                 73s                kubelet                                                       Starting kubelet.
  Normal   NodeReady                72s                kubelet                                                       Node aks-apppoolspot-31828581-vmss000001 status is now: NodeReady
  Normal   RegisteredNode           68s                node-controller                                               Node aks-apppoolspot-31828581-vmss000001 event: Registered Node aks-apppoolspot-31828581-vmss000001 in Controller
  Warning  ContainerdStart          63s (x2 over 63s)  systemd-monitor                                               Starting containerd container runtime...
  Normal   NoVMEventScheduled       41s                custom-scheduledevents-consolidated-condition-plugin-monitor  Node condition VMEventScheduled is now: Unknown, reason: NoVMEventScheduled, message: "IMDS query failed, exit code: 28\nConnection timed out after 24 seconds."
  Warning  PreemptScheduled         41s                custom-scheduledevents-consolidated-preempt-plugin-monitor    IMDS query failed, exit code: 28
Connection timed out after 24 seconds.
  Normal  NoVMEventScheduled  41s  custom-scheduledevents-consolidated-condition-plugin-monitor  Node condition VMEventScheduled is now: False, reason: NoVMEventScheduled, message: "VM has no scheduled event"

[microsoft-github-policy-service]

@Azure/aks-pm issue needs labels

[microsoft-github-policy-service]

@allyford, @justindavies, @stl327 would you be able to assist?