Envoy Gateway Addresses Common Needs for Kubernetes Ingress Traffic Handling
As Kubernetes became the accepted container orchestration solution for cloud-native applications and our systems grew in complexity and scale, the management of traffic into and within Kubernetes clusters became a critical concern.
Before the Gateway API and implementations like Envoy Gateway, cloud-native engineers used Node Ports, Load Balancers, and Ingress API Implementations to manage ingress traffic to their Kubernetes clusters.
Providing a way to expose services running in a Kubernetes cluster to external callers isn’t just about connectivity. As traffic flows, we need to manage it, secure it, and observe it. That we needed more sophisticated solutions to manage Kubernetes’ ingress traffic is not news, but it provides the history of how Envoy Gateway came about to serve common needs.
Envoy Gateway empowers you to easily configure and use the widely established Envoy Proxy for your Kubernetes ingress traffic. Envoy Proxy, an edge and service proxy designed for cloud-native applications, addresses these traffic management, security, and observability requirements.
Envoy Gateway integrates seamlessly with Kubernetes and supports the Kubernetes Gateway API, offering a robust, scalable, and flexible approach to managing ingress traffic.
When Is Envoy Gateway the Right Choice to Handle Your Kubernetes Ingress Traffic?
There are many reasons why Envoy Gateway may or may not be the right choice for your architecture. To help identify if Envoy Gateway is a good fit, here are the five top motivations for using Envoy Gateway to handle your Kubernetes Ingress traffic.
- Advanced Traffic Management: If you need advanced routing capabilities such as retries, traffic splitting, timeouts, circuit breaking, or traffic shadowing.
- Security: If you need security features like mutual TLS, rules for access control, WAF integration, and the ability to integrate with external authorization services.
- Observability: If monitoring and troubleshooting are crucial for your system, and you want observability features including detailed metrics, distributed tracing, and logging.
- Scalability: If your application needs to scale horizontally and handle high volumes of traffic, Envoy Gateway can manage this effectively.
- Compatibility with Kubernetes Gateway API: If you plan to adopt the Kubernetes Gateway API, Envoy Gateway is designed to work seamlessly with it, providing a consistent and modern API for managing Kubernetes ingress traffic configurations.
Get Started with Envoy Gateway
Envoy Gateway is ideal for modern cloud-native applications, offering robust, scalable, and flexible ingress traffic management.
Ready to optimize your Kubernetes ingress with Envoy Gateway? Speak to our experts today to learn how Envoy Gateway can elevate your infrastructure ›
###
If you’re new to service mesh, Tetrate has a bunch of free online courses available at Tetrate Academy that will quickly get you up to speed with Istio and Envoy.
Are you using Kubernetes? Tetrate Enterprise Gateway for Envoy (TEG) is the easiest way to get started with Envoy Gateway for production use cases. Get the power of Envoy Proxy in an easy-to-consume package managed by the Kubernetes Gateway API. Learn more ›
Getting started with Istio? If you’re looking for the surest way to get to production with Istio, check out Tetrate Istio Subscription. Tetrate Istio Subscription has everything you need to run Istio and Envoy in highly regulated and mission-critical production environments. It includes Tetrate Istio Distro, a 100% upstream distribution of Istio and Envoy that is FIPS-verified and FedRAMP ready. For teams requiring open source Istio and Envoy without proprietary vendor dependencies, Tetrate offers the ONLY 100% upstream Istio enterprise support offering.
Get a Demo