kubernetes-sigs/aws-load-balancer-controller

A Kubernetes controller for Elastic Load Balancers

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 16th, 2026
Created on March 10th, 2017
Open Issues & Pull Requests: 139 (+0)
GitHub issues: Enabled
Number of forks: 1,649
Total Stargazers: 4,327 (+0)
Total Subscribers: 105 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.2 hours
Mean response time: 8.0 days
90th percentile: 7.7 days
Tracked items: 561

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 6% of issues opened in the past year have never received a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "gateway-api" is answered fastest, typically in about 7 hours, while "kind/feature" waits about 2 days. 24% of tracked open issues have had no activity in three months. 66% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 90
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 466 days
Stale 30+ days: 74
Stale 90+ days: 34

Recent activity

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

Top labels

  • lifecycle/rotten (229)
  • kind/feature (114)
  • kind/bug (69)
  • kind/question (38)
  • triage/needs-investigation (37)
  • gateway-api (35)
  • kind/documentation (34)
  • triage/needs-information (32)

Detailed Description

AWS Load Balancer Controller is a Kubernetes controller that manages Elastic Load Balancers on AWS.

The controller solves the problem of integrating AWS load balancing services with Kubernetes clusters by automatically provisioning and managing Application Load Balancers and Network Load Balancers based on Ingress resources and Gateway API resources defined in the cluster. It watches for these resources and translates their specifications into corresponding AWS load balancer configurations, eliminating the need for manual load balancer setup and management outside of Kubernetes.

Teams running Kubernetes on AWS should adopt this controller if they want load balancing to be declaratively managed through standard Kubernetes APIs rather than through AWS console operations or infrastructure-as-code tools. It suits clusters of any size that need to expose services to external traffic and want that exposure defined alongside their application manifests. The controller supports both the traditional Ingress resource API and the newer Gateway API, giving teams flexibility in how they express their routing requirements.

The project maintains active development with regular commits addressing bug fixes and feature enhancements. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to test coverage and code quality standards. Documentation is kept current alongside code changes, and the project responds to reported issues with investigation and resolution. Release cycles produce stable versions at regular intervals with clear changelog documentation.