An Envoy-powered Kubernetes-native API gateway and ingress controller with function-level routing for hybrid applications.
Gloo Gateway is an Envoy-powered, Kubernetes-native API gateway and ingress controller that provides advanced traffic management for cloud-native applications. It solves the challenge of routing requests across hybrid environments by supporting microservices, serverless functions, and legacy applications through function-level routing. The gateway is fully conformant with the Kubernetes Gateway API and offers enterprise-grade features like rate limiting, security, and automated discovery.
Platform engineers, DevOps teams, and cloud architects managing Kubernetes clusters who need to implement API gateways, ingress controllers, or traffic routing for hybrid applications spanning microservices, serverless, and legacy systems.
Developers choose Gloo Gateway for its unique function-level routing capability that doesn't tie them to specific architectural paradigms, its full Kubernetes Gateway API conformance, and its ability to seamlessly integrate diverse backends while providing enterprise-grade API gateway features through Envoy proxy.
The Cloud-Native API Gateway and AI Gateway
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Unique function-level routing enables seamless integration of microservices, serverless functions, and legacy systems, as highlighted in the README for gradual migrations and multi-architecture flexibility.
Fully compliant with the Kubernetes Gateway API standard, ensuring consistent ingress management and interoperability with other Kubernetes-native tools, per the README update.
Built on Envoy proxy, it offers robust features like rate limiting, circuit breaking, and retries out of the box, providing enterprise-grade API gateway capabilities.
Continuously catalogs destinations across IaaS, PaaS, and FaaS providers, reducing manual configuration and keeping routing up-to-date, as described in the README.
Supports both Gateway API and legacy Gloo Edge APIs, which can lead to confusion and a steeper learning curve for users, as noted in the README's important update about continued support for old APIs.
With its extensive feature set and Envoy foundation, it may be over-engineered for basic ingress or routing needs, adding unnecessary overhead in straightforward Kubernetes setups.
As a project maintained by Solo.io, there's potential lock-in to their ecosystem for advanced enterprise features, and reliance on their commercial support for critical deployments.