The Cloud Native Computing Foundation (CNCF) hosts its biannual Kubecon+ CloudNativeCon conference this week, so it might come as no surprise that we’ll be hearing quite a bit of news about open-source cloud infrastructure projects in the coming days. But even a day before the event, the CNCF has a bit of news: It’s launching a new project around Envoy, the popular proxy originally developed and open-sourced by Lyft in 2016. Envoy Gateway takes the core of Envoy with a simplified deployment model and API layer to make it easier for new users to get started with Envoy as an API gateway.
In addition, the CNCF also merges two existing CNCF API gateway projects, Contour and envoy, with Envoy Gateway. Both projects were already building out API gateway features for Envoy, but the CNCF states that this new approach will allow the community to converge around a single Envoy-branded API gateway core. The new project, the organization explains in today’s announcement, aims to “rlead double efforts on security, control aircraft technicals, and other shared concerns” and let suppliers focus on building on top of Envoy and this new project rather than trying to reinvent the wheel.
The Envoy API will essentially be the Kubernetes Gateway API with Envoy-specific extensions and the overall project aims to reduce the complexity of deploying Envoy as an API gateway.
†The downside to Envoy’s success as part of many different types of architecture and vendor solutions is that it is inherently low; Envoy is not an easy piece of software to learn,” explains the CNCF. “While the project has had tremendous success with adoption by major engineering organizations around the world, it is only lightly applied for smaller and simpler use cases, where nginx and HAProxy are still dominant.”