Normally when service APIs are exposed to ingress traffic in Kubernetes, a separate routing configuration is required, such as Kubernetes Ingress Objects, Istio Virtual Services, or . Gloo Edge Virtual Services.
The HTTP configurations specified in these ingress routes must match exactly with the service APIs provided by the backend, or risk bugs, service outages, and undefined behaviors. Furthermore, correlating the traffic handled by the ingress with the APIs it exposes is a tedious task, requiring network administrators to have intricate knowledge of Developer APIs, or place the burden of network administration directly on developers.
Using this kind of “raw ingress” to track client identity and enforce policy is even more complex. Typically, API vendors wish to expose the same API functionality with policies that differ depending on the client, such as the ability to differentiate between “basic” and “premium” usage plans.
The Gloo Portal Routing features are designed to explicitly address these problems. Routing is defined in each version of an API Product. Rate limiting and authorization are defined per instance of an API Product in an Environment.
The Gloo Portal Routing features automatically configure the underlying networking implementation (Istio or Gloo Edge) using supported API Specifications as the source of configuration.
Gloo Portal users bundle and their APIs in the form of API Products and expose them through Environments, wherein they define ingress, authorization, and rate limiting policies which will automatically be attached to the exposed API endpoints.
Routes generated directly from these API Products provide per-API access logging and monitoring. These routes are automatically integrated with the Gloo Portal’s Auth Server and Rate Limiter to apply security and usage policies defined in each Environment.
Automatic Istio Routing
When targeting Istio Gateways, the Gloo Portal manages a set of Istio Custom Resource Definitions (CRDs) on behalf of users:
VirtualServices: The Gloo Portal generates an Istio VirtualService for each API Product. The VirtualService contains a single HTTP route for each API operation exposed in the product. Routes are named and their matchers are derived from the OpenAPI definition.
EnvoyFilters: The Gloo Portal generates EnvoyFilters to configure the Istio Gateway (Envoy) to communicate with the Gloo Portal ExtAuth amd RateLimit services. Additional EnvoyFilters are generated to apply per-route auth and rate limit policies.
Automatic Gloo Edge Routing
When targeting Gloo Edge, the Gloo Portal manages a set of Gloo Edge Custom Resource Definitions (CRDs) on behalf of users:
RouteTables: Gloo Portal generates a Gloo Edge
APIProductversion published in an
RouteTablewill contain an HTTP route for each API operation exposed in the
VirtualServices: Gloo Portal generates a Gloo Edge
VirtualServicewill delegate routing decisions to the
RouteTablesthat have been generated for the
APIProductversions that are published in the