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-dynamic-ephemeral-cell-routing

Envoy Gateway 1.2 Ephemeral Cell Routing via Metadata Extraction

Enforces tenant-scoped ephemeral pull request (PR) environment isolation at the network edge using declarative Envoy dynamic metadata extraction. Bypasses Kubernetes API churn and cluster-wide Envoy Gateway route reconciliations by dynamically rewriting destinations using EnvoyFilter/EnvoyExtensionPolicy metadata injection rather than provisioning per-PR HTTPRoutes.

Prohibited Anti-Pattern: Creating Static HTTPRoute Resources Per Ephemeral PR Causing Control Plane Reconciliation Storms

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Envoy Gateway 1.2 Ephemeral Cell Routing via Metadata Extraction - Enforces tenant-scoped ephemeral pull request (PR) environment isolation at the network edge using declarative Envoy dynamic metadata extraction. Bypasses Kubernetes API churn and cluster-wide Envoy Gateway route reconciliations by dynamically rewriting destinations using EnvoyFilter/EnvoyExtensionPolicy metadata injection rather than provisioning per-PR HTTPRoutes.
globs: deploy/envoy/**/*.{yaml,yml}, infrastructure/**/*.{yaml,yml}, k8s/**/*.yaml, helm/**/*.{yaml,yml}, src/infra/**/*.{ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/envoy-gateway-dynamic-ephemeral-cell-routing"
---

# Envoy Gateway 1.2 Ephemeral Cell Routing via Metadata Extraction

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Creating Static HTTPRoute Resources Per Ephemeral PR Causing Control Plane Reconciliation Storms

## System Constraints
You are a Principal Software Architect enforcing Envoy Gateway 1.2 Dynamic Ephemeral Cell Routing Standards. Ephemeral testing environments must achieve cell isolation at the edge layer without inducing Kubernetes API server thrashing or continuous Envoy xDS control-plane reconciliation cascades. You must mandate zero per-PR HTTPRoute object generation, relying strictly on declarative metadata extraction from HTTP headers, dynamic upstream host resolution, and EnvoyExtensionPolicy/EnvoyPatchPolicy rules that fall back safely to stable baseline services.

## Strict Guidelines
- Engineers MUST NEVER create, patch, or delete Kubernetes HTTPRoute objects dynamically in CI/CD pipelines to represent ephemeral pull request environments.
- Engineers MUST extract ephemeral cell routing keys (e.g., `x-pr-cell-id` or subdomain prefixes) into dynamic internal filter metadata using Envoy Gateway EnvoyExtensionPolicy or EnvoyPatchPolicy.
- Engineers MUST configure upstream cluster resolution using strict dynamic DNS or strict internal service namespaces with explicit regex validation preventing SSRF via arbitrary host injection.
- Services MUST implement a deterministic fallback mechanism that automatically directs requests lacking valid ephemeral targets to the stable canonical environment (e.g., staging).
- CI/CD pipelines MUST only deploy tenant workloads with deterministic service naming conventions (e.g., `<service>-pr-<id>.<namespace>.svc.cluster.local`) and register DNS without mutating Envoy Gateway GatewayClass or HTTPRoute state.

## Bad vs Good Implementations
### Control-Plane Reconciliation Anti-Pattern: Per-PR HTTPRoute Generation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Creating hundreds of discrete HTTPRoutes per PR forces Envoy Gateway to re-synthesize and re-push RDS/CDS updates across every Envoy proxy pod, degrading data-plane performance and risking control-plane OOM errors.
```yaml
# ANTI-PATTERN: Dynamically generating individual HTTPRoutes per PR causes
# continuous xDS reconciliation storms across the entire Envoy fleet.
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: checkout-service-pr-1422
  namespace: pr-environments
spec:
  parentRefs:
    - name: eg-shared-gateway
  hostnames:
    - "pr-1422.preview.example.com"
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /
      backendRefs:
        - name: checkout-svc-pr-1422
          port: 8080
```

#### Production Standard (Correct)
> **Standard**: A single wildcard HTTPRoute coupled with an EnvoyPatchPolicy captures ephemeral cell requests dynamically, eliminating route churn while isolating transient workloads securely at the data plane.
```yaml
# PRODUCTION INVARIANT: Single declarative wildcard route utilizing EnvoyPatchPolicy
# for zero-reconciliation dynamic cell routing based on header/subdomain extraction.
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: checkout-preview-wildcard
  namespace: preview-routing
spec:
  parentRefs:
    - name: eg-shared-gateway
  hostnames:
    - "*.preview.example.com"
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /
      backendRefs:
        - name: checkout-svc-stable
          port: 8080
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyPatchPolicy
metadata:
  name: dynamic-pr-routing-patch
  namespace: preview-routing
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: HTTPRoute
    name: checkout-preview-wildcard
  type: JSONPatch
  jsonPatches:
    - type: "envoy.filters.http.router"
      operation:
        op: add
        path: /dynamic_metadata
        value:
          envoy.filters.http.lua:
            header_matcher: "x-pr-cell-id"
            target_pattern: "checkout-svc-pr-%s.ephemeral-cells.svc.cluster.local"
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Inspector
Inspects running Gateway API and Envoy Gateway CRDs, verifying that per-PR routes are not proliferating.
Recommended Agent Skills (askills.dev)

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

Envoy Gateway CLI Helper
Validates Envoy Gateway xDS configurations, translates Gateway API CRDs to Envoy xDS, and detects reconciliation bottlenecks.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Envoy Gateway 1.2 Ephemeral Cell Routing via Metadata Extraction

Envoy Gateway 1.2 Ephemeral Cell Routing via Metadata Extraction defines an industrial-grade behavioral standard for devops engineering. Enforces tenant-scoped ephemeral pull request (PR) environment isolation at the network edge using declarative Envoy dynamic metadata extraction. Bypasses Kubernetes API churn and cluster-wide Envoy Gateway route reconciliations by dynamically rewriting destinations using EnvoyFilter/EnvoyExtensionPolicy metadata injection rather than provisioning per-PR HTTPRoutes. 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: Creating Static HTTPRoute Resources Per Ephemeral PR Causing Control Plane Reconciliation Storms 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 DriftCreating Static HTTPRoute Resources Per Ephemeral PR Causing Control Plane Reconciliation StormsCritical
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 NEVER create, patch, or delete Kubernetes HTTPRoute objects dynamically in CI/CD pipelines to represent ephemeral pull request environments.

Engineers MUST NEVER create, patch, or delete Kubernetes HTTPRoute objects dynamically in CI/CD pipelines to represent ephemeral pull request environments.

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 extract ephemeral cell routing keys (e.g., `x-pr-cell-id` or subdomain prefixes) into dynamic internal filter metadata using Envoy Gateway EnvoyExtensionPolicy or EnvoyPatchPolicy.

Engineers MUST extract ephemeral cell routing keys (e.g., `x-pr-cell-id` or subdomain prefixes) into dynamic internal filter metadata using Envoy Gateway EnvoyExtensionPolicy or EnvoyPatchPolicy.

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

Engineers MUST configure upstream cluster resolution using strict dynamic DNS or strict internal service namespaces with explicit regex validation preventing SSRF via arbitrary host injection.

Engineers MUST configure upstream cluster resolution using strict dynamic DNS or strict internal service namespaces with explicit regex validation preventing SSRF via arbitrary host injection.

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 implement a deterministic fallback mechanism that automatically directs requests lacking valid ephemeral targets to the stable canonical environment (e.g., staging).

Services MUST implement a deterministic fallback mechanism that automatically directs requests lacking valid ephemeral targets to the stable canonical environment (e.g., staging).

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

CI/CD pipelines MUST only deploy tenant workloads with deterministic service naming conventions (e.g., `<service>-pr-<id>.<namespace>.svc.cluster.local`) and register DNS without mutating Envoy Gateway GatewayClass or HTTPRoute state.

CI/CD pipelines MUST only deploy tenant workloads with deterministic service naming conventions (e.g., `<service>-pr-<id>.<namespace>.svc.cluster.local`) and register DNS without mutating Envoy Gateway GatewayClass or HTTPRoute state.

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 Ephemeral Cell Routing via Metadata Extraction critical for AI coding assistants?

Enforces tenant-scoped ephemeral pull request (PR) environment isolation at the network edge using declarative Envoy dynamic metadata extraction. Bypasses Kubernetes API churn and cluster-wide Envoy Gateway route reconciliations by dynamically rewriting destinations using EnvoyFilter/EnvoyExtensionPolicy metadata injection rather than provisioning per-PR HTTPRoutes. 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 (Creating Static HTTPRoute Resources Per Ephemeral PR Causing Control Plane Reconciliation Storms) 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