Tetrate, a company focused on simplifying Istio and Envoy for enterprise use, has announced the general availability (GA) of Tetrate Enterprise Gateway for Envoy (TEG). This release provides businesses with a modern and secure alternative to traditional Ingress controllers within Kubernetes environments.
Years in the making, this commercial version of the Envoy reverse proxy open-source project enables it to be used as a network gateway. This allows it to be used to direct internal microservices traffic and to manage external traffic coming into a Kubernetes cluster.
This project is built on top of the recent Envoy community’s release of Envoy Gateway version 1.0. TEG extends its features by including cross-cluster service discovery and load balancing, OpenID Connect (OIDC), OAuth2, Web Application Firewall (WAF), and rate limiting out of the box along with Federal Information Processing Standard (FIPS) 140-2 compliance.
A standout feature of the Envoy Gateway, and by extension TEG, is its native support for the newly introduced Kubernetes Gateway API. This modern API supersedes the older Ingress resource, offering a more expressive and extensible approach to handling ingress in Kubernetes.
TEG is easy to use — in so much as anything Kubernetes-related is easy to use! — with a quick start path and simple operations once you’re in production. It’s powered by a fully upstream Application Programming Interface (API) set for consistency and stability.
Varun Talwar, Tetrate’s co-founder, underscored the significance of this release, stating, “Tetrate is the first to deliver a simple, standardized, and powerful Envoy Gateway offering for the enterprise.” He highlighted the readiness of Envoy Gateway 1.0 and TEG for production use within Kubernetes environments, promising a future where developers are unshackled from the limitations of outdated ingress options.
Chris Aniszczyk, the Cloud Native Computing Foundation (CNCF) CTO added, “The work of committed community members in bringing projects to production readiness is key to open source sustainability and to delivering value for end users has played an instrumental role in making Envoy Gateway production-ready for Kubernetes and the wider ecosystem. We’re encouraged about what the future holds for both the project and for Kubernetes users who will deploy it as a modern standard to ingress.”
Mind you, Tetrate isn’t the only company embracing Gateway in its releases. While Linkerd boasts of its ability to add a “gateway-less” mode for cross-cluster communication in Linkerd 2.14, it has also adopted the Gateway API. Linkerd claims it’s been at the forefront of adopting Kubernetes’s new Gateway API as the core configuration mechanism.
Which of these and other rival companies will become the market leader? Stay tuned.
In the meantime, this release extends Tetrate’s product line, which includes the Tetrate Istio Subscription, Tetrate Service Express, and Tetrate Service Bridge, fortifying its position as a leader in enabling Kubernetes adopters to modernize their ingress systems with state-of-the-art, open-standard solutions.
The post Tetrate Enterprise Gateway for Envoy Graduates appeared first on The New Stack.
With this release, Envoy is ready to replace Kubernetes Ingress controllers.