One capability anyone running services in a Kubernetes cluster needs is the ability to get traffic from outside the cluster to the pods running the services inside it. A common way to do this is to use the Ingress resource and an Ingress controller. However, while the Ingress resource’s lowest-common-denominator design allows users to get started quickly, it runs into problems as you start trying to meet more advanced use cases.
That’s why the Kubernetes project has been working on the Gateway API, an expressive, extensible, role-oriented replacement for both Ingress and Service of Type Load Balancer. That’s also why the team at VMware working on Contour has been contributing to and implementing the new API. We think it’s the future of Kubernetes service networking, and we’ve found that others feel the same.
Today, we’re announcing that Contour’s VMware maintainers will be the founding members of the new Envoy Gateway project: Project Envoy’s official Service Networking solution based on Envoy and Gateway API. Read the press release here. And read more from the team working on this here.
