logo

kedacore/http-add-on

Add-on for KEDA to scale HTTP workloads

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

kedacore/http-add-on has 550+ stars and 150+ forks on GitHub, is written in Go, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):Kubernetes & OperatorsMLOps & Model DeploymentCloud Native & Infrastructure
Added to GitGenius on October 15th, 2026
Created on November 25th, 2020
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 174
Total Stargazers: 557 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.0 days
Mean response time: 32.9 days
90th percentile: 61.0 days
Tracked items: 142

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

10 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 10% of issues opened in the past year have never received a reply. Work labelled "enhancement" is answered fastest, typically in about 2 days, while "stale-bot-ignore" waits about 3 weeks. 83% of issues opened in the past year have been closed, leaving a working backlog. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 387 days
Stale 30+ days: 12
Stale 90+ days: 8

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (56)
  • enhancement (35)
  • stale (29)
  • stale-bot-ignore (21)
  • help wanted (10)
  • governance (7)
  • needs-triage (7)
  • documentation (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

HTTP Add-on is a Kubernetes autoscaler that scales HTTP workloads based on incoming traffic patterns.

The HTTP Add-on solves the problem of scaling HTTP servers in Kubernetes without a built-in HTTP-based scaler in KEDA's core. It enables automatic scaling up and down of HTTP workloads, including scaling to zero replicas when traffic is absent. The tool intercepts HTTP traffic to measure request volume and uses these metrics to drive scaling decisions through KEDA's event-driven autoscaling framework.

Teams running HTTP services on Kubernetes who want traffic-driven autoscaling should consider this tool. It suits projects that need to respond dynamically to HTTP demand without manual intervention or external monitoring systems. The project is in beta with a v1.0 release planned, meaning it is stable for use though minor breaking changes to deployment manifests or configuration may occur. A commercially supported alternative exists for teams requiring vendor backing.

The project maintains active end-to-end testing infrastructure. Security practices follow established best practices frameworks. The codebase is published and tracked against security standards. Community engagement occurs through documented discussion channels and contribution guidelines.