Gloo OSS will reach end of life on December 31st, 2026. After that date, it will no longer receive releases, bug fixes, or security patches.

Gloo OSS has had an incredible journey as the Kubernetes-native API gateway, built on top of Envoy Proxy. In late 2024, we donated Gloo OSS, rebranded as kgateway, to the Cloud Native Computing Foundation (CNCF), giving the project a new home in the broader open source ecosystem. Since then, we have continued providing regular releases across all supported versions to give users time to plan their migration. With the EOL date now set, we encourage all users to complete that migration before December 31st, 2026.

The move to kgateway represents everything Gloo OSS was, and more: full alignment with the Kubernetes Gateway API standard, a thriving open source community under the CNCF umbrella, and a roadmap built around the next generation of cloud-native networking. It is the natural successor to Gloo OSS, and we believe it is the right home for this project's future.

If you are still running Gloo OSS, we strongly encourage you to migrate to kgateway: https://kgateway.dev

Thanks to everyone who contributed to Gloo OSS over the years, the issues raised, the PRs merged, the docs improved, and the community built around it. None of this would have been possible without you.

Important Gloo Gateway is now a fully conformant Kubernetes Gateway API implementation!

The existing Gloo Edge APIs were not changed and continue to be fully supported.

Gloo Gateway is a feature-rich, fast, and flexible Kubernetes-native ingress controller and next-generation API gateway that is built on top of Envoy proxy and the Kubernetes Gateway API. It excels in function-level routing, supports legacy apps, microservices and serverless, offers robust discovery capabilities, integrates seamlessly with open-source projects, and is designed to support hybrid applications with various technologies, architectures, protocols, and clouds.

Installation   |   Documentation   |   Blog   |   Slack   |   Twitter |   Enterprise Trial

• Kubernetes Gateway API: Gloo Gateway is a feature-rich ingress controller, built on top of the Envoy Proxy and fully conformant with the Kubernetes Gateway API.
• Next-generation API gateway: Gloo Gateway provides a long list of API gateway features including rate limiting, circuit breaking, retries, caching, transformation, service-mesh integration, security, external authentication and authorization.
• Hybrid apps: Gloo Gateway creates applications that route to backends implemented as microservices, serverless functions and legacy apps. This feature can help users to
  • Gradually migrate from their legacy code to microservices and serverless.
  • Add new functionalities using cloud-native technologies while maintaining their legacy codebase.
  • Allow different teams in an organization choose different architectures.

• Function-level routing allows integration of legacy applications, microservices and serverless: Gloo Gateway can route requests directly to functions. Request to Function can be a serverless function call (e.g. Lambda, Google Cloud Function, OpenFaaS Function, etc.), an API call on a microservice or a legacy service (e.g. a REST API call, OpenAPI operation, XML/SOAP request etc.), or publishing to a message queue (e.g. NATS, AMQP, etc.). This unique ability is what makes Gloo Gateway the only API gateway that supports hybrid apps as well as the only one that does not tie the user to a specific paradigm.
• Gloo Gateway incorporates vetted open-source projects to provide broad functionality: Gloo Gateway supports high-quality features by integrating with top open-source projects, including gRPC, OpenTelemetry, NATS and more. Gloo Gateway's architecture allows rapid integration of future popular open-source projects as they emerge.
• Full automated discovery lets users move fast: Upon launch, Gloo Gateway creates a catalog of all available destinations and continuously keeps them up to date. This takes the responsibility for 'bookkeeping' away from the developers and guarantees that new features become available as soon as they are ready. Gloo Gateway discovers across IaaS, PaaS and FaaS providers as well as Swagger and gRPC.

• Join us on our Slack channel: https://slack.solo.io/
• Follow us on Twitter: https://twitter.com/soloio_inc
• Check out the docs: https://docs.solo.io/gateway/latest/

The devel folder should be the starting point for understanding the code, and contributing to the product.

Gloo Gateway would not be possible without the valuable open-source work of projects in the community. We would like to extend a special thank-you to Envoy.

Reporting security issues : We take Gloo Gateway's security very seriously. If you've found a security issue or a potential security issue in Gloo Gateway, please DO NOT file a public Github issue, instead send your report privately to security@solo.io.