Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time

Table of Contents generated with DocToc

Kubernetes-based Event Driven Autoscaling - HTTP Add-on

The KEDA HTTP Add-on allows Kubernetes users to automatically scale their HTTP servers up and down (including to/from zero) based on incoming HTTP traffic. Please see our use cases document to learn more about how and why you would use this project.

🚧 Project status: on-hold/beta 🚧
📢 KEDA is actively looking for contributors to help maintain the add-on and maintainers will make a decision about future of the add-on at the end of November. Learn more in this discussion.

The HTTP Add-on currently is in beta. We can't yet recommend it for production usage because we are still developing and testing it. It may have "rough edges" including missing documentation, bugs and other issues. It is currently provided as-is without support.

HTTP Autoscaling Made Simple

KEDA provides a reliable and well tested solution to scaling your workloads based on external events. The project supports a wide variety of scalers - sources of these events, in other words. These scalers are systems that produce precisely measurable events via an API.

KEDA does not, however, include an HTTP-based scaler out of the box for several reasons:

  • The concept of an HTTP "event" is not well defined.
  • There's no out-of-the-box single system that can provide an API to measure the current number of incoming HTTP events or requests.
  • The infrastructure required to achieve these measurements is more complex and, in some cases, needs to be integrated into the HTTP routing system in the cluster (e.g. the ingress controller).

For these reasons, the KEDA core project has purposely not built generic HTTP-based scaling into the core.

This project, often called KEDA-HTTP, exists to provide that scaling. It is composed of simple, isolated components and includes an opinionated way to put them together.

Adopters - Become a listed KEDA user!

We are always happy to start list users who run KEDA's HTTP Add-on in production or are evaluating it, learn more about it here.

We welcome pull requests to list new adopters.


Although this is currently a beta release project, we have prepared a walkthrough document with instructions on getting started for basic usage.

See that document at docs/


The HTTP Add-on is composed of multiple mostly independent components. This design was chosen to allow for highly customizable installations while allowing us to ship reasonable defaults.

  • We have written a complete design document. Please see it at docs/
  • For more context on the design, please see our scope document.
  • If you have further questions about the project, please see our FAQ document.


Please see the complete installation instructions.


We use GitHub issues to build our backlog, a complete overview of all open items and our planning.

Learn more about our roadmap.


This project follows the KEDA contributing guidelines, which are outlined in

If you would like to contribute code to this project, please see docs/

We are a Cloud Native Computing Foundation (CNCF) incubation project.

Code of Conduct

Please refer to the organization-wide Code of Conduct document.