AWS Load Balancer Controller adds general availability support for Kubernetes Gateway API
What started the discussion
This r/kubernetes thread focused on AWS Load Balancer Controller adds general availability support for Kubernetes Gateway API. The original post pointed readers to aws.amazon.com, and the comments quickly turned into a practical discussion about the tradeoffs, surprises, and production realities behind the topic.
What stood out in the comments
Discussion point 1
Lots of folks , like myself are currently migrating to gateway api from Nginx ingress since it is EOL after this month.
Discussion point 2
Cool, this is especially important now that nginx ingress is on the way out
Discussion point 3
Does it matter that much? Gateway API is literally designed to abstract away things that were vendor specific. I don't know of anything that Ingress supports that Gateway doesn't. You should be planning a move to Gateway API.
Discussion point 4
Im using: AWS Load Balancer Controller + Gateway API + Envoy Gateway
Discussion point 5
Will this finally make target group deregistration less stupid? Having to do pre-stop sleep with extra signals so targets can stop getting traffic before shutting down is painfully annoying.
Thread snapshot
- Original subreddit: r/kubernetes
- Original author: u/swe129
- Reddit score: 89
- Comment count: 23
- Original thread: https://aws.amazon.com/blogs/networking-and-content-delivery/aws-load-balancer-controller-adds-general-availability-support-for-kubernetes-gateway-api/