What happens to Pod-Workload if a Node gets destroyed

Question

when running pod-workload on an AKS-cluster with autoscaling enabled, what happens, if the pool gets scaled down? If a Pod is running workload on a node, and this node is being removed because of nodepool-scaledown, how does AKS manage to keep my pod running until the workload is finished?

Even if there is a re-scheduling, this would interrupt my workload, which would lead to a failure in my case.

So how does K8s know, when a Node is "ready" to be scaled down ?

Answer 1

Hi previousversiondocs,

If a node considered to be removed then the Kubernetes will run extra pod before deleting the main pod to avoid disruption in the workloads.

Also, you can use pod disruption budget which will schedule extra pods on other nodes before deleting the running pods to avoid any downtime.

You can also see the cluster auto scaler FAQs which explains the behavior when scale up or scale down happens.

Hope this helps, and please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.