Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
This might be true for "stock" Kubernetes, but it seems likely that the grandparent post is using cluster autoscaling (since they mention "auto-scaled up"), for which this post is not accurate. The cluster-autoscaler component does remove nodes with low utilization and Pods fitting onto other nodes, effectively defragging the cluster. There's just plenty of reasons for it to not drain a node (as per its FAQ[1]). But it's highly configurable, so I wonder if the grandparent post just needed some configuration changes to suit their scenario better.
[1] https://github.com/kubernetes/autoscaler/blob/master/cluster...
You might want to take a look at descheduler: https://github.com/kubernetes-sigs/descheduler