Skip to main content
Account

Kuadrant

Kuadrant adds rate limiting, authentication, TLS and multi-cluster DNS policies to Gateway API. Learn how its policy CRDs work with Istio and Envoy Gateway.

Status
Stable
Category
Orchestration & Management
Subcategory
API Gateway
License
Apache-2.0
Technology matrix Skip Just not for me See the matrix

Kuadrant is a set of Kubernetes Gateway API policy extensions that add rate limiting, authentication, authorization, and multi-cluster DNS/TLS to any Gateway API implementation. It does not ship its own gateway; instead it attaches policies to existing Istio or Envoy Gateway installations.

The core CRDs are AuthPolicy, RateLimitPolicy, DNSPolicy, and TLSPolicy, all of which attach to a Gateway or HTTPRoute via the Gateway API policy attachment pattern. Auth and rate limit policies are enforced by two sub-components โ€” Authorino (an ext_authz service backed by OPA/CEL-like expressions, supporting OIDC, API keys, mTLS, OPA Rego) and Limitador (a Redis-backed ext_ratelimit service implementing the Envoy ratelimit protocol). Because these are standard Envoy extension points, the same policies work across any Envoy-based Gateway API implementation. DNSPolicy and TLSPolicy, paired with a multi-cluster gateway setup, handle GSLB-style failover and cert-manager integration across clusters.

Kuadrant is developed by Red Hat and shares heritage with 3scale. Compared to a bespoke API management product (Kong, Apigee, 3scale on-premises), Kuadrant is specifically the Kubernetes-native, CRD-driven version layered on open Gateway API rather than a separate proxy and control plane.

API Gateway

Email signup loads here. You can also manage email preferences in account settings.

Build Kuadrant? I'll show you where engineers get stuck with it โ†’ Back free content for the community โ†’