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-quic-stateless-reset-migration

Envoy Gateway HTTP/3 QUIC Stateless Reset Token & Session Migration Invariant

Enforces deterministic, cryptographically shared QUIC stateless reset tokens and active connection migration routing across distributed Envoy ingress deployments. Prevents silent session termination, 4-way handshake restarts, and blackholed UDP packets when mobile clients transition across cellular and Wi-Fi networks.

Prohibited Anti-Pattern: Ephemerally Seeded Stateless Reset Tokens and Uncoordinated QUIC Connection ID Routing

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Envoy Gateway HTTP/3 QUIC Stateless Reset Token & Session Migration Invariant - Enforces deterministic, cryptographically shared QUIC stateless reset tokens and active connection migration routing across distributed Envoy ingress deployments. Prevents silent session termination, 4-way handshake restarts, and blackholed UDP packets when mobile clients transition across cellular and Wi-Fi networks.
globs: k8s/**/*.yaml, infrastructure/**/*.yaml, deploy/**/*.yaml, gateway/**/*.yaml, config/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/envoy-gateway-quic-stateless-reset-migration"
---

# Envoy Gateway HTTP/3 QUIC Stateless Reset Token & Session Migration Invariant

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Ephemerally Seeded Stateless Reset Tokens and Uncoordinated QUIC Connection ID Routing

## System Constraints
You are a Principal Platform Engineer and L4/L7 Network Architect enforcing strict Envoy Gateway API HTTP/3 QUIC invariants. You must prevent connection drops and stateless reset desynchronization during network path migration (e.g., cellular LTE/5G to Wi-Fi) by guaranteeing synchronized stateless reset keys, stable QUIC connection ID encoding algorithms, and Maglev/eBPF-consistent UDP load balancing across all distributed Envoy pods.

## Strict Guidelines
- Engineers MUST ALWAYS configure a shared cryptographically random token secret via Kubernetes Secrets mounted into Envoy Gateway EnvoyProxy configurations for quicProtocol stateless reset token generation across distributed pods.
- Engineers MUST NOT allow Envoy instances to generate localized ephemeral stateless reset token secrets, as migrated packets landing on an alternate ingress pod will cause unrecoverable peer resets.
- Platform configs MUST enforce deterministic QUIC Connection ID (CID) generation lengths and routing keys to enable upstream Layer 4 load balancers (Cilium eBPF / Maglev) to steer migrated 4-tuples back to the originating Envoy worker thread or pod.
- Services MUST enable QUIC connection migration explicitly with active_connection_migration enabled within the EnvoyProxy transport socket protocol options.
- Components NEVER expose HTTP/3 over raw UDP NodePort load balancers without symmetric session affinity or consistent 5-tuple routing bypassing CID-aware L4 dispatchers.

## Bad vs Good Implementations
### EnvoyProxy HTTP/3 QUIC Stateless Reset and Migration Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Each replica generates its own localized ephemeral key for stateless reset tokens. When a mobile client undergoes active connection migration from cellular to Wi-Fi, the client 4-tuple changes. Packets directed to a different ingress pod fail signature checks, emitting erroneous Stateless Reset tokens that violently tear down live HTTP/3 streams.
```yaml
# INSECURE & FRAGILE: Default ephemeral QUIC setup without shared reset token or migration support
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: ingress-edge
  namespace: envoy-gateway-system
spec:
  telemetry:
    accessLog:
      settings:
        - format:
            type: Text
  provider:
    type: Kubernetes
    kubernetes:
      envoyDeployment:
        replicas: 10 # Multi-pod ingress without coordinated QUIC state
        container:
          resources:
            limits:
              cpu: "2"
              memory: 2Gi
# Omission of quicSettings, connection ID router, and shared token leads to dropped migrated flows
```

#### Production Standard (Correct)
> **Standard**: Configures a synchronized Kubernetes secret for distributed QUIC stateless reset generation and enables deterministic Connection ID generation. Alternate pods receiving migrated 5-tuple UDP traffic successfully identify active sessions or authenticate stateless resets without discarding legitimate client network handovers.
```yaml
# RESILIENT: Coordinated QUIC Stateless Reset Secret with Connection Migration Enabled
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: ingress-edge
  namespace: envoy-gateway-system
spec:
  provider:
    type: Kubernetes
    kubernetes:
      envoyDeployment:
        replicas: 10
  extraArgs:
    - "--enable-core-dump"
  quic:
    statelessResetTokenSecret:
      name: envoy-shared-stateless-reset-key
    connectionId:
      generator: deterministic
      length: 16
  bootstrap:
    type: Merge
    value: | # Envoy bootstrap patch ensuring QUIC active connection migration is active
      static_resources:
        listeners:
          - name: envoy_quic_listener
            protocol: UDP
            udp_listener_config:
              quic_options:
                enable_active_migration: true
                connection_id_generator_config:
                  name: envoy.quic.deterministic_cid_generator
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Validator MCP
Inspects and audits EnvoyGateway and Gateway API CRDs against production QUIC protocol constraints.
Recommended Agent Skills (askills.dev)

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

Envoy QUIC and UDP Route Auditor
Validates cross-cluster ingress CID configurations and verifies stateless reset secret distribution across pods.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Envoy Gateway HTTP/3 QUIC Stateless Reset Token & Session Migration Invariant

Envoy Gateway HTTP/3 QUIC Stateless Reset Token & Session Migration Invariant defines an industrial-grade behavioral standard for devops engineering. Enforces deterministic, cryptographically shared QUIC stateless reset tokens and active connection migration routing across distributed Envoy ingress deployments. Prevents silent session termination, 4-way handshake restarts, and blackholed UDP packets when mobile clients transition across cellular and Wi-Fi networks. 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: Ephemerally Seeded Stateless Reset Tokens and Uncoordinated QUIC Connection ID Routing 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 DriftEphemerally Seeded Stateless Reset Tokens and Uncoordinated QUIC Connection ID RoutingCritical
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 a shared cryptographically random token secret via Kubernetes Secrets mounted into Envoy Gateway EnvoyProxy configurations for quicProtocol stateless reset token generation across distributed pods.

Engineers MUST ALWAYS configure a shared cryptographically random token secret via Kubernetes Secrets mounted into Envoy Gateway EnvoyProxy configurations for quicProtocol stateless reset token generation across distributed pods.

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 allow Envoy instances to generate localized ephemeral stateless reset token secrets, as migrated packets landing on an alternate ingress pod will cause unrecoverable peer resets.

Engineers MUST NOT allow Envoy instances to generate localized ephemeral stateless reset token secrets, as migrated packets landing on an alternate ingress pod will cause unrecoverable peer resets.

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

Platform configs MUST enforce deterministic QUIC Connection ID (CID) generation lengths and routing keys to enable upstream Layer 4 load balancers (Cilium eBPF / Maglev) to steer migrated 4-tuples back to the originating Envoy worker thread or pod.

Platform configs MUST enforce deterministic QUIC Connection ID (CID) generation lengths and routing keys to enable upstream Layer 4 load balancers (Cilium eBPF / Maglev) to steer migrated 4-tuples back to the originating Envoy worker thread or pod.

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

Services MUST enable QUIC connection migration explicitly with active_connection_migration enabled within the EnvoyProxy transport socket protocol options.

Services MUST enable QUIC connection migration explicitly with active_connection_migration enabled within the EnvoyProxy transport socket protocol options.

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

Components NEVER expose HTTP/3 over raw UDP NodePort load balancers without symmetric session affinity or consistent 5-tuple routing bypassing CID-aware L4 dispatchers.

Components NEVER expose HTTP/3 over raw UDP NodePort load balancers without symmetric session affinity or consistent 5-tuple routing bypassing CID-aware L4 dispatchers.

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 HTTP/3 QUIC Stateless Reset Token & Session Migration Invariant critical for AI coding assistants?

Enforces deterministic, cryptographically shared QUIC stateless reset tokens and active connection migration routing across distributed Envoy ingress deployments. Prevents silent session termination, 4-way handshake restarts, and blackholed UDP packets when mobile clients transition across cellular and Wi-Fi networks. 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 (Ephemerally Seeded Stateless Reset Tokens and Uncoordinated QUIC Connection ID Routing) 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