Policies · Kong Mesh
MeshGlobalRateLimit
Kong Mesh rate limiting backed by an external rate-limit service shared across proxies.
Behaviour per target
Output: MeshGlobalRateLimit
Copied unchanged with an advisory: removed in 3.0 with no in-mesh replacement. A leftover
object is not rejected; it enforces nothing. Plan rate limiting at the gateway or with
MeshRateLimit.
No output kind.
Copied to _manual/, not to the apply tree, and listed under
"Delete Before Upgrading to 3.0". Remove the ratelimit.* / global.ratelimit.* Helm
overrides, and delete the meshglobalratelimits.kuma.io CRD after upgrading (Helm leaves
it in place).
Timeline
| Version | Change |
|---|---|
| 3.0 | Removed with its control-plane support, the Helm rate-limit service and the KMESH_GLOBAL_RATE_LIMIT_* settings. Leftover objects become inert. |
Related topics
- Access control — MeshTrafficPermission from[] versus SPIFFE rules[], MeshOPA, and the Kong Mesh RBAC changes in 3.0 — what kuma-migrator converts and what stays manual.