2 years ago

Category: Database, Data, Microsoft, Kubernetes, Hashicorp

KEDA consists of two primary components, the KEDA agent that activates and deactivates Kubernetes deployments to scale to and from zero, and the metrics server, which exposes event data to the Horizontal Pod Autoscaler to scale out. KEDA can be added to any Kubernetes cluster, providing event-driven autoscaling based on data as provided by a scaler, which serves as an integration between KEDA and a variety of databases, messaging systems, telemetry systems, CI/CD and more. During its time in the sandbox, KEDA increased the number of available scalers from 15 to 37, and KEDA maintainer Tom Kerkhove says that more are on the way.

This is because of a Kubernetes limitation, and Kerkhove said that “what we’re trying to do is look at that Kubernetes limitation and see if we can fix that, so that both Kubernetes and KEDA now benefit from it.”

We’re trying to see if there’s a place in the community to introduce a new standard for traffic metrics so that KEDA can rely on one specification and basically serve the full customer base and with all the scenarios,” said Kerkhove.