Gloo is an Envoy-powered API gateway and ingress controller built by Solo.io as a cloud-native solution for Kubernetes environments. Written primarily in Go, the project implements the Kubernetes Gateway API specification and serves as both a feature-rich ingress controller and next-generation API gateway. The repository is classified across multiple domains including service mesh, microservices, canary deployments, traffic shifting, load balancing, observability, traffic management, routing, and security.
The core functionality of Gloo centers on function-level routing, which distinguishes it from conventional API gateways. This capability allows requests to be routed directly to various backend types including serverless functions like AWS Lambda or Google Cloud Functions, microservice APIs, legacy applications, and message queues such as NATS or AMQP. This hybrid application support enables organizations to gradually migrate from legacy systems to cloud-native architectures while maintaining existing codebases, allowing different teams to adopt different architectural paradigms simultaneously.
Gloo Gateway recently achieved full conformance with the Kubernetes Gateway API specification while maintaining backward compatibility with existing Gloo Edge APIs. The platform provides comprehensive API gateway features including rate limiting, circuit breaking, retries, caching, request transformation, service mesh integration, security controls, and external authentication and authorization mechanisms. The architecture emphasizes integration with vetted open-source projects, incorporating technologies like gRPC, OpenTelemetry, and NATS to deliver broad functionality without vendor lock-in.
A distinctive feature of Gloo is its automated discovery system, which creates and continuously maintains a catalog of available destinations across IaaS, PaaS, and FaaS providers. This discovery extends to Swagger and gRPC specifications, reducing manual configuration burden and ensuring new services become available to the gateway automatically upon deployment. The platform is designed to support hybrid applications spanning various technologies, architectures, protocols, and cloud providers.
The repository shows active maintenance and community engagement. GitGenius tracking data reveals a median issue and pull request response latency of 0.6 hours with a mean of 32.4 hours across 7334 tracked items, indicating responsive project management. The most active contributor tracked is nfuden with 6896 events, followed by ilrudie with 149 events and sheidkamp with 49 events. The project maintains active security practices, with stale issues being the most frequently tracked label at 180 occurrences, followed by trivy and vulnerability labels each appearing 58 times, reflecting attention to dependency management and security vulnerability tracking.
The repository maintains connections with related projects through overlapping contributors, linking to github/gh-aw, kgateway-dev/kgateway, and longhorn/longhorn. Documentation is comprehensive, with a dedicated devel folder serving as the entry point for understanding the codebase and contributing to the project. The project emphasizes security, requesting that potential security issues be reported privately to [email protected] rather than through public GitHub issues, demonstrating a mature approach to vulnerability disclosure.
