Can a node autoscaler automatically start an extra pod when replica count is 1 & minAvailable is also 1?

our autoscaling (horizontal and vertical) works pretty fine, except the downscaling is not working somehow (yeah, we checked the usual suspects like https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#i-have-a-couple-of-nodes-with-low-utilization-but-they-are-not-scaled-down-why ).

Since we want to save resources and have pods which are not ultra-sensitive, we are setting following

Deployment

replicas: 1

PodDisruptionBudget

minAvailable: 1

HorizontalPodAutoscaler

minReplicas: 1maxReplicas: 10

But it seems now that this is the problem that the autoscaler is not scaling down the nodes (even though the node is only used by 30% by CPU + memory and we have other nodes which have absolutely enough memory + cpu to move these pods).

Is it possible in general that the auto scaler starts an extra pod on the free node and removes the old pod from the old node?