AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
devopscritical PriorityID: envoy-gateway-partition-resilient-rate-limit-invariant

Envoy Gateway 1.2 Multi-Cluster Partition-Resilient Rate Limit Guardrail

Cross-region edge ingress must enforce a local token-bucket rate limit layer alongside global rate limiting policies within Envoy Gateway 1.2. In the event of cross-region network partitions or central rate-limit cluster degradation, local rate limiting guarantees deterministic traffic shedding to protect downstream backends from thundering herds.

Prohibited Anti-Pattern: Global-Only Rate Limiting Failing Open During Cross-Region Partitions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Envoy Gateway 1.2 Multi-Cluster Partition-Resilient Rate Limit Guardrail - Cross-region edge ingress must enforce a local token-bucket rate limit layer alongside global rate limiting policies within Envoy Gateway 1.2. In the event of cross-region network partitions or central rate-limit cluster degradation, local rate limiting guarantees deterministic traffic shedding to protect downstream backends from thundering herds.
globs: **/gateway/**/*.yaml, **/envoy-gateway/**/*.yaml, **/k8s/**/*.yaml, **/ingress/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/envoy-gateway-partition-resilient-rate-limit-invariant"
---

# Envoy Gateway 1.2 Multi-Cluster Partition-Resilient Rate Limit Guardrail

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Global-Only Rate Limiting Failing Open During Cross-Region Partitions

## System Constraints
You are a Principal Infrastructure Engineer enforcing Envoy Gateway 1.2 multi-cluster partition-resilient rate limit invariants. Mandate that all ingress gateway configurations pairing global rate limiting with cross-region dependencies specify autonomous local token-bucket rate limit fallbacks.

## Strict Guidelines
- Engineers MUST ALWAYS configure local token-bucket rate limiting alongside global rate limit policies within BackendTrafficPolicy or ClientTrafficPolicy resources.
- Engineers MUST NOT configure global rate limit clusters with `failClosed: false` without a corresponding deterministic local token bucket bounding peak regional ingress.
- Global rate limit configurations MUST specify a bounded client-side timeout (`timeout: 20ms` to `50ms`) to avoid saturating Envoy connection pools during WAN brownouts.
- Local rate limit policies MUST match or strictly undercut the maximum provisioned downstream backend cluster capacity per region.
- Ingress Gateway configurations MUST export metrics for `rate_limit.local_rate_limit.*` and `rate_limit.global_rate_limit.*` to detect partition transitions immediately.

## Bad vs Good Implementations
### Configuring Global RLS with Autonomous Local Rate Limit Fallback in Envoy Gateway 1.2

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: This policy depends entirely on central global rate limiters without specifying an autonomous local rate limit. If the cross-region link to the rate limit service drops, Envoy gateway fails open, exposing backends to unbounded request surges.
```yaml
# INSECURE: Single global rate limit cluster with fail-open semantics.
# During WAN partition to central Redis/RLS, ingress permits unlimited throughput,
# causing cascading failure across regional backend pods.
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: BackendTrafficPolicy
metadata:
  name: edge-rate-limit
  namespace: ingress-system
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: HTTPRoute
    name: regional-api-route
  rateLimit:
    global:
      rules:
        - clientSelectors:
            - headers:
                - type: Distinct
                  name: X-Forwarded-For
          limit:
            requests: 1000
            unit: Minute
      # Omits local rate limiting fallback and defaults to unbounded fail-open
```

#### Production Standard (Correct)
> **Standard**: Configures a 30ms timeout on global rate limiting and enforces a local rate limit rule. If the global rate limit service partitions, the local token bucket bounds maximum ingress throughput to survivable local capacity.
```yaml
# RESILIENT: Dual-tier rate limiting with local token-bucket fallback.
# Local limit caps regional traffic even if central RLS drops.
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: BackendTrafficPolicy
metadata:
  name: edge-rate-limit
  namespace: ingress-system
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: HTTPRoute
    name: regional-api-route
  rateLimit:
    global:
      timeout: 30ms
      rules:
        - clientSelectors:
            - headers:
                - type: Distinct
                  name: X-Forwarded-For
          limit:
            requests: 1000
            unit: Minute
    local:
      rules:
        - limit:
            requests: 500
            unit: Second
      default:
        requests: 200
        unit: Second
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Kubernetes Resource Inspector
Inspect and validate Gateway API and Envoy Gateway CRD manifests directly against the target cluster.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Envoy Gateway CLI (egctl)
Translates and verifies Envoy Gateway custom resources and dumps effective Envoy xDS configurations to validate rate-limit filter order.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Envoy Gateway 1.2 Multi-Cluster Partition-Resilient Rate Limit Guardrail

Envoy Gateway 1.2 Multi-Cluster Partition-Resilient Rate Limit Guardrail defines an industrial-grade behavioral standard for devops engineering. Cross-region edge ingress must enforce a local token-bucket rate limit layer alongside global rate limiting policies within Envoy Gateway 1.2. In the event of cross-region network partitions or central rate-limit cluster degradation, local rate limiting guarantees deterministic traffic shedding to protect downstream backends from thundering herds. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Global-Only Rate Limiting Failing Open During Cross-Region Partitions Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftGlobal-Only Rate Limiting Failing Open During Cross-Region PartitionsCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS configure local token-bucket rate limiting alongside global rate limit policies within BackendTrafficPolicy or ClientTrafficPolicy resources.

Engineers MUST ALWAYS configure local token-bucket rate limiting alongside global rate limit policies within BackendTrafficPolicy or ClientTrafficPolicy resources.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT configure global rate limit clusters with `failClosed

Engineers MUST NOT configure global rate limit clusters with `failClosed: false` without a corresponding deterministic local token bucket bounding peak regional ingress.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Global rate limit configurations MUST specify a bounded client-side timeout (`timeout

Global rate limit configurations MUST specify a bounded client-side timeout (`timeout: 20ms` to `50ms`) to avoid saturating Envoy connection pools during WAN brownouts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Local rate limit policies MUST match or strictly undercut the maximum provisioned downstream backend cluster capacity per region.

Local rate limit policies MUST match or strictly undercut the maximum provisioned downstream backend cluster capacity per region.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Ingress Gateway configurations MUST export metrics for `rate_limit.local_rate_limit.*` and `rate_limit.global_rate_limit.*` to detect partition transitions immediately.

Ingress Gateway configurations MUST export metrics for `rate_limit.local_rate_limit.*` and `rate_limit.global_rate_limit.*` to detect partition transitions immediately.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Envoy Gateway 1.2 Multi-Cluster Partition-Resilient Rate Limit Guardrail critical for AI coding assistants?

Cross-region edge ingress must enforce a local token-bucket rate limit layer alongside global rate limiting policies within Envoy Gateway 1.2. In the event of cross-region network partitions or central rate-limit cluster degradation, local rate limiting guarantees deterministic traffic shedding to protect downstream backends from thundering herds. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Global-Only Rate Limiting Failing Open During Cross-Region Partitions) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related DEVOPS Rules

View all rules →
devops
86

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

devops
118

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

devops
40

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

Envoy