aws-load-balancer-controller
AWS Load Balancer Controller Helm chart for Kubernetes
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
Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.
Availability: platform listings confirmed today
No GitHub repository data collected yet.
Resources & Compatibility
Requirements not published yet.
First-install notes
No first-install notes yet.
Variants
Alternatives
No alternatives collected yet.
Common questions
How can I avoid the controller creating a new load balancer for every Ingress deployment?
The provided thread says the poster’s workaround is to have teams create a separate Ingress and load balancer first, then attach further Ingress resources to it.
Can I check the controller’s webhook configuration if the controller itself is not responding?
Yes; fetching the aws-load-balancer-webhook validating webhook configuration queries the Kubernetes API server and does not require a functional controller. A slow response may mean the API server is busy or other webhooks are delaying the response.
Which AWS Systems Manager runbook helps diagnose ALB or NLB provisioning problems for the controller?
The AWSSupport-TroubleshootEKSALBControllerIssues runbook helps diagnose common issues that prevent the controller from properly provisioning and managing ALB and NLB for Kubernetes Ingresses and Services.
What controller-level failure areas are covered by the scaling and performance troubleshooting guidance?
It covers controller-level problems, resource reconciliation failures, AWS integration issues, and debugging techniques.
Answers sourced from deepwiki.com, docs.aws.amazon.com, github.com, www.reddit.com
Community
No community discussions collected yet.