Autoscaling inference with KEDA and custom metrics
Scale on queue depth, not CPU. Your wallet will thank you.
DO
Daniel Okoro
Jun 10, 2026·1 min read·90
CPU-based autoscaling is meaningless for GPU inference. The right signal is how many requests are waiting.
triggers:
- type: prometheus
metadata:
query: sum(inference_queue_depth)
threshold: "10"Scale to zero, carefully
Scaling to zero saves money overnight, but cold starts hurt. Keep one warm replica for latency-sensitive tiers and let batch tiers go cold.
Warm pool for interactive traffic.
Cold scale-to-zero for batch.
Pre-pull images to cut cold-start minutes.
DO
Written by
Daniel OkoroStaff SRE — Kubernetes & scaling
I write about running stateful inference workloads on Kubernetes without losing sleep.
4 followers · 2 stories