Webinar Recap – What’s New in Gloo API Gateway version 1.5
Gloo is a next generation API gateway and Kubernetes Ingress Controller built on Envoy Proxy to manage and secure application traffic at the edge. Recently we released version 1.5 which includes new features, enhancements, and bug fixes for Gloo API Gateway, Federation, and Developer Portal. You can read more about the latest release, here and check out the docs.
In our latest webinar, we covered the latest 1.5 release, including:
- Enhanced Multi-Cluster Failover in Gloo Federation
- Traffic Routing and Route Table Enhancements
- More Config Options for Gloo, Envoy, and a Dry-Run Validation API
- Security Improvements for External Authentication
- Improvements for Configuring and Enforcing Rate Limits
- Enhanced AWS Lambda Integration
- Developer and Operator Experience enhancements
Watch the replay here
Highlights from the Q&A
Is Rate Limiting available in open source or enterprise or both?
Both open source and enterprise versions of Gloo API gateway offer rate limiting, but a little bit differently.
The open source version allows you provide your own implementation. We expose Envoy’s rate limiting filter which which can be configured to look at any gRPC service that implements the rate limit API to make rate limiting decisions.
The enterprise version comes with our implementation of the gRPC service that has functionality built into the CRDs and inline configs. We’ve also included things on top like weights, rules, and handling sets rather than rate limit trees.
Can you use multiple OIDC providers with the Developer Portal?
Each Developer Portal application can integrate with one OIDC provider. You can deploy multiple developer portals in your environment (maybe one per application) with each portal using a different auth provider. Read the docs for more info here.
Do you support OpenAPIU and Swagger?
The Developer Portal supports OpenAPI and you can import your existing OpenAPI documents into the portal to become your API catalog. After importing, you can choose how to expose those APIs to the API products including a one-to-one mapping or even merging to documents together. View the sample OpenAPI document used in the demo, here.
How does the API Product work with CRDs (Custom Resources)?
All of the objects demoed in the webinar for the Developer Portal are Kubernetes CRDs. Everything that you saw in the UI can be driven declaratively with YAML. In fact, Gloo’s entire configuration is driven by CRDs making it Kubernetes-native in design and configuration.