Scale Kubernetes deployments to zero using KEDA

If you have a multi-cluster EKS deployment for your development, QA and staging environments, those generally don't need to run at 3AM. No one is using any of that, except for maybe a few cronjobs to refresh data. Everything else is wasted idle compute. The math is simple. A dev cluster running 24/7 bills for 168 hours a week. Trim it to office hours, weekdays only, and you're down to roughly 55. That's about two thirds of the compute spend on every environment nobody actively uses, and it stacks per cluster. For us that's dev, QA and staging. The stock HPA can't really help with this; it scales on load, and its hard floor is one replica. It can't take your workloads to zero. There are multiple ways to scale down your deployments to zero to make sure you don't waste that money. Recently I started using KEDA and a cron scaler to do the work for me. KEDA is short for Kubernetes Event-Driven Autoscaling. It's an intelligent autoscaler that can integrate with Prometheus, VictoriaMetrics…