Research & Papers

Intelligent Cluster Optimizer blocks autoscaling when memory leaks detected

New open-source K8s operator uses linear regression to detect memory leaks and block harmful auto-scaling.

Deep Dive

A team of researchers (Azra Karakaya, Erva Şengül, Ahmet Kaplan) published a paper introducing the Intelligent Cluster Optimizer, an open-source Kubernetes operator designed to solve resource over-provisioning with safety as a first-class concern. The core contribution is a five-layer safety pipeline that combines SLA monitoring, a circuit breaker, HPA/PDB conflict detection, a policy engine, and a memory-leak detector based on linear regression with R² scoring. Unlike typical predictive autoscalers that only alert on anomalies, this system actively blocks scaling recommendations when a memory leak is detected, preventing the operator from masking software defects by granting more resources to a leaking workload.

The system uses percentile analysis and Holt-Winters forecasting to generate right-sizing recommendations, balanced through multi-objective Pareto optimization at the per-container level. It also includes rollback and dry-run modes for human approval. The researchers validated the operator with 1,118 automated tests (80.3% code coverage) and a live deployment on Google Kubernetes Engine. Their what-if projections estimated cost savings of 20–40% from right-sizing, while the leak gate achieved 83% detection accuracy. This approach turns anomaly detection from a passive alerting tool into an active safety gate, a novel contribution for Kubernetes resource optimization.

Key Points
  • Five-layer safety pipeline includes a memory-leak detector using linear regression with R² scoring that blocks scaling recommendations on leak detection.
  • Validated with 1,118 automated tests (80.3% coverage) and a live GKE deployment, showing 83% leak detection accuracy and 20–40% projected cost savings.
  • Combines percentile analysis, Holt-Winters forecasting, and Pareto optimization for per-container right-sizing with rollback and dry-run modes.

Why It Matters

Prevents autoscaling from hiding memory leaks, cutting cloud costs while maintaining reliability in Kubernetes clusters.

📬 Get the top 10 AI stories daily