ScaleOps, a company that provides cloud resource management solutions, has announced the general availability of Pod Placement, a capability that provides ongoing optimization of Kubernetes clusters. 

According to the company, Kubernetes clusters often have workloads with scheduling and eviction constraints that are permanently tied to specific computing nodes, and these eviction rules can block resource consolidation and force organizations to maintain excess capacity.

“After deploying to over a thousand production clusters, the new Pod Placement capability automatically identified that more than 40% contained unevictable workloads creating systemic inefficiencies that traditional optimization tools simply couldn’t address,” said Guy Baron, co-founder and CTO of ScaleOps. “In many cases, we found that strict pod disruption budgets were responsible for nearly 50% more resources than necessary because the cluster autoscaler couldn’t consolidate the nodes effectively. Pod Placement is the first solution to solve this at the scheduling layer, working in harmony with existing Kubernetes components while delivering immediate value. Early adopters have seen their node counts drop significantly while maintaining strict availability requirements.”

Pod Placement optimizes the scheduling of unevictable pods, and groups them together and schedules them on a set of common nodes. This maximizes Bin Packing efficiency, increases, cluster utilization, and reduces the overall allocated resources, the company explained. 

It also provides insight and visibility into the different constraints that may be preventing cluster resources from being fully utilized.

Pod Placement works alongside the default Kubernetes Schedule, or with any Cluster Auto Scaler, the company said. 

“After providing value to many of our customers during the beta program while gathering feedback and performing rigorous real-world validation, ScaleOps is proud to offer this game-changing solution as a production-ready feature for all our customers,” the Baron wrote in a blog post