[edude03]

Rescheduler is impractical because scheduling is environment specific. You might have for example a database that needs three nodes and you have three servers, there's no where to reschedule those pods to in that case.

In the cloud you can use cluster autoscaler or karpenter to automatically handle the unhomed pods however.

[AntiUSAbah]

What happens is, that when one node goes down, the pod gets removed and moves to another node. The node comes backup but k8s doesn't rebalance that pod despite having an anti-affinity.

For me, that this feature doesn't exist in core k8s, is bad. It should be able to do so. Controllable for sure.

[edude03]

It does, you need to drain the node before removing it otherwise kube assumes the node will come back