<ul data-eligibleForWebStory="false"><li>Kubernetes Ingress has been the standard method for routing HTTP(S) traffic into clusters but has limitations with complex use cases.</li><li>The Gateway API is introduced as a modern, expressive standard to replace Ingress over time.</li><li>Key differences include support for multiple protocols, native traffic splitting, standardized cross-namespace delegation, role separation, and extensibility.</li><li>Migration to Gateway API involves evaluating controller support, starting with HTTPRoute, testing functionality, incremental migration, and automating translation.</li></ul>

Kubernetes Gateway API vs Ingress: The New Standard for Traffic Routing

Discover more