aws-load-balancer-controller
Kubernetes controller that provisions and manages AWS Application and Network Load Balancers in response to Ingress, Service, and Gateway API resources.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
74/100 Good
- Maintained
- 100last commit 17 days ago
- Popular
- 734,343 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 4,343
- Open issues
- 129
- Last commit
- 2026-11-03
- Latest release
- v3.6.2
- License
- Apache-2.0
- Activity
- declining
Checked 16 days ago - source: GitHub (kubernetes-sigs/aws-load-balancer-controller)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Migration note Users of the legacy AWS ALB Ingress Controller must uninstall it before installing AWS Load Balancer Controller; follow the provided migration guide. source
Fetched 16 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How can I troubleshoot the controller failing to provision or manage an ALB or NLB on EKS?
Use the AWSSupport-TroubleshootEKSALBControllerIssues automation runbook, which helps diagnose common issues that prevent the controller from properly provisioning and managing ALBs and NLBs for Kubernetes ingresses and services.
How can I avoid creating a new load balancer for every Ingress deployment?
One shared workaround is to have teams create a separate Ingress and load balancer first, then attach further Ingress resources to it.
Where do I find installation-specific options versus runtime configuration options?
Runtime configuration options are covered in the controller configurations documentation, while installation-specific configuration options are covered in the Helm chart values documentation.
Answers sourced from docs.aws.amazon.com, github.com, www.reddit.com
Community
Collected 16 days ago - public community threads