AWS shipped GA support for Kubernetes Gateway API in its Load Balancer Controller, dumping annotation-based configuration for type-safe CRDs with proper validation. The release handles both L4 (TCP/UD

InfoQ is a leading online platform for software developers, architects, and technical leaders, providing news, articles, presentations, and interviews on a wide range of topics, including agile practices, DevOps, microservices, and emerging technologies. With a focus on quality content and expert insights, InfoQ helps professionals stay informed about the latest trends, best practices, and industry developments. Developers can learn from real-world experiences, gain  knowledge, and connect with peers in the global software community through InfoQ's diverse and engaging content.

InfoQ

AWS has shipped GA support for the Kubernetes Gateway API in its Load Balancer Controller (v3.1.0). The release replaces annotation-based load balancer configuration with type-safe Custom Resource Definitions (CRDs), covering both Layer 4 (TCP/UDP via NLB) and Layer 7 (HTTP/gRPC via ALB) routing. Key features include cross-namespace routing, automatic TLS certificate discovery from ACM, and role-separated RBAC so developers don't need cluster-admin permissions. Three new CRDs — TargetGroupConfiguration, LoadBalancerConfiguration, and ListenerRuleConfiguration — validate at apply time rather than failing silently at runtime. Existing Ingress resources remain supported and are not deprecated. Teams on EKS running v2.13.3+ (L4) or v2.14.0+ (L7) can enable Gateway API support via feature flags.

AWS Load Balancer Controller Reaches GA with Kubernetes Gateway API Support