Create ScaledObject
1. Target
2. Configuration
3. Triggers

The default option is apps/v1, but you can customize the apiVersion. Example: argoproj.io/v1alpha1.

The default options are Deployment and StatefulSet, but you can customize the kind to any kind that has the scale subresource. Example: Rollout

Documentation
Deployments and StatefulSets are the most common way to scale workloads with KEDA.
It allows you to define the Kubernetes Deployment or StatefulSet that you want KEDA to scale based on a scale trigger. KEDA will monitor that service and based on the events that occur, it will automatically scale your resource by adding or removing replicas accordingly.
Behind the scenes, KEDA acts to monitor the event source and feed that data to Kubernetes and the HPA (Horizontal Pod Autoscaler) to drive rapid scale of a resource. Each replica of a resource is actively pulling items from the event source. With KEDA and scaling Deployments/StatefulSet you can scale based on events while also preserving rich connection and processing semantics with the event source (e.g. in-order processing, retries, deadletter, checkpointing).
© 2026 Kedify Inc.