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: k8s-gateway-api-spiffe-canary-mtls-invariants

Kubernetes Gateway API Dynamic Canary Splitting & SPIFFE mTLS Invariants

Enforces strict Kubernetes Gateway API (v1) configuration invariants for progressive canary rollouts and zero-trust cryptographic service identity validation. Mandates deterministic traffic weight normalization, cross-namespace ReferenceGrant authorization, and strict SPIFFE x509 SVID validation via BackendTLSPolicy without relying on proprietary service mesh sidecars.

Prohibited Anti-Pattern: Unvalidated Cross-Namespace Canary Routing with Insecure Cleartext Upstreams

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kubernetes Gateway API Dynamic Canary Splitting & SPIFFE mTLS Invariants - Enforces strict Kubernetes Gateway API (v1) configuration invariants for progressive canary rollouts and zero-trust cryptographic service identity validation. Mandates deterministic traffic weight normalization, cross-namespace ReferenceGrant authorization, and strict SPIFFE x509 SVID validation via BackendTLSPolicy without relying on proprietary service mesh sidecars.
globs: k8s/**/*.yaml, deploy/**/*.yaml, infra/**/*.yaml, charts/**/*.yaml, manifests/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/k8s-gateway-api-spiffe-canary-mtls-invariants"
---

# Kubernetes Gateway API Dynamic Canary Splitting & SPIFFE mTLS Invariants

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unvalidated Cross-Namespace Canary Routing with Insecure Cleartext Upstreams

## System Constraints
You are a Principal DevOps and Zero-Trust Security Architect enforcing Kubernetes Gateway API standards and SPIFFE/SPIRE identity invariants. You must prevent unauthenticated backend routing, cross-namespace hijacking, and non-deterministic canary traffic distribution. Mandate strict BackendTLSPolicy with SPIFFE subjectAlternativeName (SAN) matching, mandatory ReferenceGrants for multi-tenant namespace references, and deterministic sum-normalized weights across all HTTPRoute backendRefs.

## Strict Guidelines
- Engineers MUST ALWAYS enforce Gateway API v1 (gateway.networking.k8s.io/v1) and explicitly define relative integer weights on every backendRef within HTTPRoute canary rules that resolve to a deterministic integer sum.
- Engineers MUST ALWAYS attach a BackendTLSPolicy to canary backends specifying explicit validation rules, CA certificate references (ConfigMap), and strict SAN validation matching the expected SPIFFE ID (spiffe://<trust-domain>/ns/<namespace>/sa/<serviceaccount>).
- Engineers MUST NOT allow cross-namespace backendRefs in an HTTPRoute unless a corresponding ReferenceGrant exists in the target namespace explicitly permitting the Gateway/HTTPRoute group and kind.
- Engineers MUST NEVER route production traffic to plain HTTP Services without mutual TLS verification when routing between distinct security zones or namespaces.
- Canary HTTPRoutes SHOULD include session affinity/cookie stickiness or consistent hashing directives alongside weight splits to prevent session shearing across baseline and canary versions during stateful interactions.
- All SPIFFE Subject Alternative Names (SANs) MUST be exact string matches or adhere strictly to spiffe:// URI schemes; wildcard SANs (*.spiffe) or unvalidated DNS names MUST be rejected.

## Bad vs Good Implementations
### HTTPRoute Canary Weight and Cross-Namespace SPIFFE BackendTLSPolicy

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The bad example routes cross-namespace traffic without verifying ReferenceGrant authorization, relies on implicit/implementation-dependent backend weights causing unpredictable canary splits, and omits BackendTLSPolicy, leaving internal traffic subject to cleartext spoofing and unverified TLS identities.
```yaml
# INSECURE: Undefined weights, unvalidated cross-namespace route, and cleartext routing
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: payment-route
  namespace: ingress-gw
spec:
  parentRefs:
    - name: edge-gateway
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /pay
      backendRefs:
        - name: payment-service-stable
          namespace: payments
          port: 8080
          # Missing weight: defaults to implementation-dependent distribution
        - name: payment-service-canary
          namespace: payments
          port: 8080
          # Missing ReferenceGrant in 'payments' namespace permits route hijacking
          # Missing BackendTLSPolicy transmits plaintext tokens over the cluster fabric
```

#### Production Standard (Correct)
> **Standard**: The secure configuration provides a ReferenceGrant authoring cross-namespace bindings, explicitly defines normalized integer weights (90/10), and binds a BackendTLSPolicy validating the SPIFFE SVID URI SAN against the trusted SPIRE bundle.
```yaml
# SECURE: Deterministic weights, explicit ReferenceGrant, and SPIFFE SAN validated BackendTLSPolicy
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-gw-to-payment
  namespace: payments
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: ingress-gw
  to:
    - group: ""
      kind: Service
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: payment-route
  namespace: ingress-gw
spec:
  parentRefs:
    - name: edge-gateway
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /pay
      backendRefs:
        - name: payment-service-stable
          namespace: payments
          port: 8443
          weight: 90
        - name: payment-service-canary
          namespace: payments
          port: 8443
          weight: 10
---
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: BackendTLSPolicy
metadata:
  name: payment-canary-tls
  namespace: payments
spec:
  targetRefs:
    - group: ""
      kind: Service
      name: payment-service-canary
  validation:
    caCertificateRefs:
      - group: ""
        kind: ConfigMap
        name: spire-bundle
    hostname: payment-service-canary.payments.svc.cluster.local
    subjectAltNames:
      - type: URI
        uri: spiffe://prod.internal/ns/payments/sa/payment-canary-sa
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Controller MCP
Enables inspection, validation, and real-time schema validation of Gateway API CRDs and active cluster HTTPRoute status.
Recommended Agent Skills (askills.dev)

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

Kubeconform Gateway API Strict Validator
Validates Kubernetes manifests against latest Gateway API v1 CRD schemas including BackendTLSPolicy and ReferenceGrant.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kubernetes Gateway API Dynamic Canary Splitting & SPIFFE mTLS Invariants

Kubernetes Gateway API Dynamic Canary Splitting & SPIFFE mTLS Invariants defines an industrial-grade behavioral standard for devops engineering. Enforces strict Kubernetes Gateway API (v1) configuration invariants for progressive canary rollouts and zero-trust cryptographic service identity validation. Mandates deterministic traffic weight normalization, cross-namespace ReferenceGrant authorization, and strict SPIFFE x509 SVID validation via BackendTLSPolicy without relying on proprietary service mesh sidecars. 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: Unvalidated Cross-Namespace Canary Routing with Insecure Cleartext Upstreams 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 DriftUnvalidated Cross-Namespace Canary Routing with Insecure Cleartext UpstreamsCritical
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 enforce Gateway API v1 (gateway.networking.k8s.io/v1) and explicitly define relative integer weights on every backendRef within HTTPRoute canary rules that resolve to a deterministic integer sum.

Engineers MUST ALWAYS enforce Gateway API v1 (gateway.networking.k8s.io/v1) and explicitly define relative integer weights on every backendRef within HTTPRoute canary rules that resolve to a deterministic integer sum.

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 ALWAYS attach a BackendTLSPolicy to canary backends specifying explicit validation rules, CA certificate references (ConfigMap), and strict SAN validation matching the expected SPIFFE ID (spiffe

Engineers MUST ALWAYS attach a BackendTLSPolicy to canary backends specifying explicit validation rules, CA certificate references (ConfigMap), and strict SAN validation matching the expected SPIFFE ID (spiffe://<trust-domain>/ns/<namespace>/sa/<serviceaccount>).

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 NOT allow cross-namespace backendRefs in an HTTPRoute unless a corresponding ReferenceGrant exists in the target namespace explicitly permitting the Gateway/HTTPRoute group and kind.

Engineers MUST NOT allow cross-namespace backendRefs in an HTTPRoute unless a corresponding ReferenceGrant exists in the target namespace explicitly permitting the Gateway/HTTPRoute group and kind.

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

Engineers MUST NEVER route production traffic to plain HTTP Services without mutual TLS verification when routing between distinct security zones or namespaces.

Engineers MUST NEVER route production traffic to plain HTTP Services without mutual TLS verification when routing between distinct security zones or namespaces.

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

Canary HTTPRoutes SHOULD include session affinity/cookie stickiness or consistent hashing directives alongside weight splits to prevent session shearing across baseline and canary versions during stateful interactions.

Canary HTTPRoutes SHOULD include session affinity/cookie stickiness or consistent hashing directives alongside weight splits to prevent session shearing across baseline and canary versions during stateful interactions.

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.
6

All SPIFFE Subject Alternative Names (SANs) MUST be exact string matches or adhere strictly to spiffe

All SPIFFE Subject Alternative Names (SANs) MUST be exact string matches or adhere strictly to spiffe:// URI schemes; wildcard SANs (*.spiffe) or unvalidated DNS names MUST be rejected.

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 Kubernetes Gateway API Dynamic Canary Splitting & SPIFFE mTLS Invariants critical for AI coding assistants?

Enforces strict Kubernetes Gateway API (v1) configuration invariants for progressive canary rollouts and zero-trust cryptographic service identity validation. Mandates deterministic traffic weight normalization, cross-namespace ReferenceGrant authorization, and strict SPIFFE x509 SVID validation via BackendTLSPolicy without relying on proprietary service mesh sidecars. 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 (Unvalidated Cross-Namespace Canary Routing with Insecure Cleartext Upstreams) 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

Kubernetes