As of today we offer KEDA as a default component for horizontally scaling your Pods.
Horizontal Pod Autoscaling, based on CPU and Memory metrics, was already possible through the standard Kubernetes HPA. However our customers asked for more possibilities, with an emphasis on Amazon SQS-based autoscaling.
Based on this feedback we’re now deploying KEDA to offer this functionality (and much more).
From the upstream project:
KEDA is a [Kubernetes](https://kubernetes.io/)-based Event Driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needing to be processed.
KEDA is a single-purpose and lightweight component that can be added into any Kubernetes cluster. KEDA works alongside standard Kubernetes components like the Horizontal Pod Autoscaler and can extend functionality without overwriting or duplication. With KEDA you can explicitly map the apps you want to use event-driven scale, with other apps continuing to function. This makes KEDA a flexible and safe option to run alongside any number of any other Kubernetes applications or frameworks.
See our public documentation, next to the upstream documentation for more info and examples on how to use it.
Actions
KEDA uses the Kubernetes HPA under the hood.
Although not required, we recommend you to try out KEDA CPU and Memory scalers if you were using the HPA before.
Important: In any case make sure you don’t define both HPA HorizontalPodAutoscaler and KEDA ScaledObject resources for scaling the same workload as they will compete with each other and this will result in odd scaling behavior.