Kubernetes has become the standard platform for deploying cloud-native applications, but networking and traffic management remain challenging, particularly with the limitations of the existing Ingress resource, which focuses mainly on Layer 7 HTTP/HTTPS traffic. Ingress simplifies external access management by centralizing control, but its lack of standardization and support for non-HTTP protocols, as well as advanced traffic management features, often leads to fragmentation and vendor-specific implementations. To address these issues, the Gateway API project introduces a set of new, portable network management resources designed to unify capabilities across different Ingress controllers, offering support for both Layer 4 and Layer 7 protocols, advanced traffic management features, and expanded rule customization. This new API aims to provide a standardized model that enhances portability, reduces vendor lock-in, and offers developers expanded declarative management capabilities. While the Gateway API will complement existing Ingress controllers, it is expected to gradually replace vendor-specific implementations with its comprehensive and flexible approach, supporting a wide range of use cases across both cloud and on-premise environments.