Session
Autoscaling Isn't Set-and-Forget: Tuning KEDA & Karpenter for Real Workloads
You've deployed KEDA and Karpenter, now what? Most talks stop at "it scales." This one starts there. We'll dive into the advanced configurations, failure modes, and optimization patterns that separate demo clusters from production workloads. On the Karpenter side: Node Disruption Budgets to control voluntary disruptions, how to survive Spot interruptions gracefully, and bootstrap optimizations that shave minutes off node startup. On KEDA: scaling modifiers that combine multiple metrics into smarter decisions, cooldown tuning to prevent thrashing, and the shift from reactive scaling to proactive workload sizing. We'll show how Karpenter and KEDA changes the equation: what you get out of the box, what you still need to configure, and how all of this fits into building an efficient Kubernetes cluster.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top