The Intelligent Cluster Optimizer is an open-source Kubernetes operator that right-sizes container workloads with safety as a first-class concern, and combines SLA monitoring, a circuit breaker, HPA/PDB conflict detection, and a policy engine, with rollback and dry-run mode for human approval.
Abstract
Kubernetes is the standard platform for orchestrating containerized applications, yet resource management remains difficult. To stay safe, engineers over-provision CPU and memory, leaving reserved but unused capacity that is the main source of wasted cost. The built-in Horizontal and Vertical Pod Autoscalers are reactive: they act only after a threshold is crossed, which causes lag, over-provisioning, and can mask software defects by granting a leaking workload more memory. Predictive autoscalers focus on improving forecasting accuracy or run inside proprietary infrastructure, and anomaly detection is used only to alert, never to block a harmful action. The Intelligent Cluster Optimizer is an open-source Kubernetes operator that right-sizes container workloads with safety as a first-class concern. Its central contribution is a five-layer safety pipeline where a memory-leak detector, based on linear regression with R^2 scoring, acts as a blocking gate: if a leak is detected the recommendation is rejected, so the optimizer never hides a bug by enlarging a broken container. The pipeline combines SLA monitoring, a circuit breaker, HPA/PDB conflict detection, and a policy engine, with rollback and dry-run mode for human approval. Recommendations are produced by percentile analysis and Holt-Winters forecasting, balanced through multi-objective Pareto optimization at the per-container level. We validated the system with 1118 automated tests at 80.3% coverage and a live deployment on Google Kubernetes Engine, where right-sizing produced estimated cost savings of 20--40% in what-if projections and the leak gate reached 83% detection accuracy.
Rust-for-Linux (R4L) is landing storage code in mainline, but per-driver migration decisions are still largely a judgment call: maintainers must weigh historical bug exposure, residual unsafe surface, dynamic robustness, and execution cost without a shared evidence pipeline. We propose KOxI, an evidence-gated pipeline...
Guilherme Lima, Tomaz Mikio Sasaki· Proceedings of the 18th ACM...· 0 citations
Kubernetes 1.35 stabilized in-place Pod resource resizing, but a deployable controller must avoid duplicate actuation, decline infeasible changes safely, and make blocked actions distinguishable from controller failure. This paper presents Elastic Pod CPU Auto-Scaler (EPCAS), an open-source operator for restart-sensiti...
H. Rajagopal, Kavya Vishwanath, Daniel Shafer et al.· IEEE Access· 0 citations
OpScale is presented, a practical operator-level orchestration framework of profiling, provisioning, placement, and runtime serving that attains SLOs with up to 36.3% fewer GPUs and 28% less power, or achieves 44% higher throughput under fixed cost budgets.
Xingqi Cui, Chieh-Jan Mike Liang, Ziang T. Tang et al.· 0 citations
Intent-Based Networking (IBN) enables operators to express high-level service objectives that are automatically translated into low-level control and orchestration policies. In AI-native 6G management planes, semantic misalignment during this translation can induce unsafe configurations that amplify conventional resour...
Nilesh Chakraborty, P. Djukic, Burak Kantarci· IEEE Transactions on Network...· 0 citations
Large language model (LLM) inference deployed on Kubernetes faces an autoscaling challenge that conventional web services do not: new serving replicas take two to ten minutes to start because multi-gigabyte model weights must be loaded, which makes purely reactive scaling structurally late. We ask a sharp question: amo...
Tian-Rui Liu, Xiao-Hai Hu· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.