AWS Load Balancer Controller
Helm chart for the AWS Load Balancer Controller, a Kubernetes controller that automatically creates and manages Elastic Load Balancers on Amazon Web Services…
Platform availability
Available on 1 of 9 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)
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 0 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
No GitHub repository data collected yet.
Resources & Compatibility
Requirements not published yet.
First-install notes
- Check the landing zone status After you start creating your AWS landing zone, check the get-landing-zone-operation status. If it says IN_PROGRESS, wait until it finishes, because moving on too early can leave accounts and policies half-set-up and break later steps. source
- Keep custom SCP files where the manifest expects them Put custom SCP (service control policy) JSON files, like block-s3-public.json, in the folder structure your manifest references. If the file is missing or placed in the wrong spot, AWS Control Tower setup can fail or the permission rule won’t be applied. source
- Get exact baseline ARNs before changing them Use the list or filter commands to copy the exact baseline ARN (the long identifier) before applying or resetting a baseline. If you use the wrong ARN, the command can miss the right OU or account and cause confusing failures. source
- Prepare AWS permissions Deploy the chart into an Amazon Web Services Kubernetes cluster and ensure the controller's service account has permissions to create and modify Elastic Load Balancers. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How should the controller's service account be prepared before deploying the Helm chart?
The controller's service account needs permissions to create and modify Elastic Load Balancers in AWS.
Which AWS load balancer type does the controller provision for Ingress, Service, and Gateway resources?
Ingress resources are satisfied with Application Load Balancers, Service resources with Network Load Balancers, and Gateway resources with either Network or Application Load Balancers.
What mitigation has been discussed for preventing a new load balancer from being created for every Ingress?
One user described a process workaround: have teams first create a dedicated Ingress and load balancer, then attach additional Ingress resources to it.
What failure has been reported when the controller manages shared backend security groups?
A reported issue described the controller revoking all shared backend security group rules during pod churn due to a stale security group cache race, causing a cluster-wide outage.
Answers sourced from github.com, github.com, www.reddit.com
Community
No community discussions collected yet.