tag: Gateway-Api · 2 items
- Platform/SRE — Plan: EKS Auto Mode now natively manages Gateway API resources (Gateway, HTTPRoute) including weighted routing, header-based routing, and ACM TLS — eliminating the need for a separate ingress controller. Evaluate adopting Gateway/HTTPRoute as the standard traffic-management pattern for EKS Auto Mode clusters this quarter.
- CI/CD — Skip
- Leader — Learn: EKS Auto Mode’s native Gateway API support signals Kubernetes standardizing on a single next-gen ingress model; worth tracking as a data point when reviewing golden-path networking standards for EKS-based platforms.
- Platform/SRE — Plan: TCPRoute and UDPRoute are now stable in the v1 API, making portable L4 routing viable for production workloads like databases, DNS, and VoIP. If you’re already using experimental Gateway API resources, audit for the new gateway.networking.x-k8s.io API group separation to avoid breakage on upgrade.
- CI/CD — Skip
- Leader — Learn: Gateway API continues maturing as the unified Kubernetes networking standard; L4 GA coverage strengthens the case for standardizing on it as the org’s golden-path ingress model over implementation-specific CRDs.