We'll release a whole new version of AWS ALB Ingress Controller while rename it to be "AWS Load Balancer Controller" with below new features:
- IngressGroup: ability to support multiple Kubernetes Ingresses with a single Application Load Balancer.
- NLB-IP Service: ability to support Kubernetes Service with Network Load Balancer and IP Targeting.
- TargetGroupBinding: a new CRD which allows to bind a Kubernetes service endpoints to a TargetGroup.
AWS Load Balancer Controller RC releases are available: v2.0.0-rc3
Warning: RC releases are not suitable for production usage. For production usage, please use AWS ALB Ingress Controller before we released the GA version.
NOTE: The current image version is v1.1.9. Please file any issues you find and note the version used.
The AWS ALB Ingress Controller satisfies Kubernetes ingress resources by provisioning Application Load Balancers.
This project was originated by Ticketmaster and CoreOS as part of Ticketmaster's move to AWS and CoreOS Tectonic. Learn more about Ticketmaster's Kubernetes initiative from Justin Dean's video at Tectonic Summit.
This project was donated to Kubernetes SIG-AWS to allow AWS, CoreOS, Ticketmaster and other SIG-AWS contributors to officially maintain the project. SIG-AWS reached this consensus on June 1, 2018.
Checkout our Live Docs!
To get started with the controller, see our walkthrough.
- See controller setup on how to install ALB ingress controller
- See external-dns setup for how to setup the external-dns to manage route 53 records.
For details on building this project, see our building guide.
Learn how to engage with the Kubernetes community on the community page.
You can reach the maintainers of this project at:
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.
