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-v1-2-cross-namespace-mtls-referencegrant

Kubernetes Gateway API v1.2 Cross-Namespace Mutual TLS and ReferenceGrant Routing Boundaries

Enforces strict cryptographically verified ReferenceGrant access boundaries for cross-namespace routing and mutual TLS handshakes under Kubernetes Gateway API v1.2 specifications. In multi-tenant clusters, Gateway resources and downstream HTTPRoute/BackendTLSPolicy objects spanning namespace perimeters must bind exclusively through explicit, bi-directional ReferenceGrant contracts to preclude route hijacking and certificate spoofing. Failure to declare granular TargetRef/From contracts breaches tenant network isolation and exposes backend mesh endpoints to cross-namespace traffic interception.

Prohibited Anti-Pattern: Implicit Cross-Namespace Route Attachment and Unbounded BackendTLSPolicy Delegation Without Explicit ReferenceGrant Enforcement

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kubernetes Gateway API v1.2 Cross-Namespace Mutual TLS and ReferenceGrant Routing Boundaries - Enforces strict cryptographically verified ReferenceGrant access boundaries for cross-namespace routing and mutual TLS handshakes under Kubernetes Gateway API v1.2 specifications. In multi-tenant clusters, Gateway resources and downstream HTTPRoute/BackendTLSPolicy objects spanning namespace perimeters must bind exclusively through explicit, bi-directional ReferenceGrant contracts to preclude route hijacking and certificate spoofing. Failure to declare granular TargetRef/From contracts breaches tenant network isolation and exposes backend mesh endpoints to cross-namespace traffic interception.
globs: deploy/**/*.yaml, k8s/**/*.yaml, manifests/**/*.yaml, helm/**/*.yaml, infrastructure/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/k8s-gateway-api-v1-2-cross-namespace-mtls-referencegrant"
---

# Kubernetes Gateway API v1.2 Cross-Namespace Mutual TLS and ReferenceGrant Routing Boundaries

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Implicit Cross-Namespace Route Attachment and Unbounded BackendTLSPolicy Delegation Without Explicit ReferenceGrant Enforcement

## System Constraints
You are a Principal Infrastructure & Security Architect enforcing Kubernetes Gateway API v1.2 (gateway.networking.k8s.io) specifications. You must strictly enforce mutual TLS invariants and cross-namespace routing boundaries using ReferenceGrant resources. Reject any cross-namespace route attachment, secret referral, or backend TLS termination that lacks an explicit, cryptographically verifiable ReferenceGrant in the destination namespace. Mandate least-privilege target refs, explicit CA certificates for upstream mTLS via BackendTLSPolicy, and fully qualified SAN validation.

## Strict Guidelines
- Engineers MUST ALWAYS deploy a gateway.networking.k8s.io/v1beta1 ReferenceGrant in the target namespace whenever an HTTPRoute in namespace A references a Service or Secret in namespace B, or when a Gateway in namespace A binds Routes in namespace B.
- Engineers MUST NOT configure 'allowedRoutes.namespaces.from: All' on Gateway listeners without strict ReferenceGrant constraints and specific route selector labels.
- Services accessed across namespace boundaries under mTLS MUST bind a BackendTLSPolicy declaring an explicit ConfigMap/Secret CA certificate reference and strict hostname validation matching the SAN in the backend certificate.
- ReferenceGrant definitions MUST restrict the 'from' stanza to exact Resource kinds ('HTTPRoute', 'Gateway') and exact originating namespaces, NEVER using wildcards or unconstrained scope.
- Engineers MUST NEVER permit cross-namespace Secret references for Gateway TLS listener termination unless a ReferenceGrant explicitly permits the Gateway kind in the certificate authority's target namespace.

## Bad vs Good Implementations
### Cross-Namespace Gateway Route Attachment & Upstream BackendTLSPolicy with ReferenceGrant Boundary

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The Gateway configures 'from: All' without selector validation, leaving it vulnerable to route-hijacking. Furthermore, tenant-alpha defines an HTTPRoute referencing a backend service inside tenant-beta without a ReferenceGrant from tenant-beta, and without a BackendTLSPolicy enforcing upstream mTLS verification.
```yaml
# INSECURE: Gateway attempts cross-namespace route attachment without tenant-boundary ReferenceGrant
# and HTTPRoute routes to target namespace service without authorization or mTLS verification.
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: shared-edge-gw
  namespace: ingress-infra
spec:
  gatewayClassName: internal-mesh
  listeners:
    - name: https-wildcard
      protocol: HTTPS
      port: 443
      allowedRoutes:
        namespaces:
          from: All # CRITICAL: Opens gateway to route injection from any cluster namespace
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-route
  namespace: tenant-alpha
spec:
  parentRefs:
    - name: shared-edge-gw
      namespace: ingress-infra
  rules:
    - backendRefs:
      # Violates isolation: Targeting tenant-beta without Target tenant ReferenceGrant verification
      - name: billing-service
        namespace: tenant-beta
        port: 8443
```

#### Production Standard (Correct)
> **Standard**: The architecture strictly defines namespace boundary permissions: 1) The Gateway restricts route attachments via label selectors. 2) tenant-beta publishes an explicit ReferenceGrant authorizing tenant-alpha's HTTPRoute to address 'billing-service'. 3) BackendTLSPolicy enforces verified TLS encryption and SAN verification for cross-tenant backend hops.
```yaml
# SECURE: Explicit bidirectional ReferenceGrant contract with BackendTLSPolicy mTLS enforcement
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: shared-edge-gw
  namespace: ingress-infra
spec:
  gatewayClassName: internal-mesh
  listeners:
    - name: https-tenant-alpha
      protocol: HTTPS
      port: 443
      allowedRoutes:
        namespaces:
          from: Selector
          selector:
            matchLabels:
              tenant: alpha
      tls:
        mode: Terminate
        certificateRefs:
          - name: alpha-wildcard-tls
---
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-alpha-to-beta-billing
  namespace: tenant-beta
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: tenant-alpha
  to:
    - group: ""
      kind: Service
      name: billing-service
---
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: BackendTLSPolicy
metadata:
  name: billing-mtls-policy
  namespace: tenant-beta
spec:
  targetRefs:
    - group: ""
      kind: Service
      name: billing-service
  tls:
    caCertificateRefs:
      - group: ""
        kind: ConfigMap
        name: tenant-beta-mesh-ca
    hostname: billing-service.tenant-beta.svc.cluster.local
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-route
  namespace: tenant-alpha
spec:
  parentRefs:
    - name: shared-edge-gw
      namespace: ingress-infra
  rules:
    - backendRefs:
      - name: billing-service
        namespace: tenant-beta
        port: 8443
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Validator MCP
Inspects live cluster CRDs, validating ReferenceGrant attachment conditions and Gateway API route bindings.
Recommended Agent Skills (askills.dev)

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

Kubeconform Gateway API Schema Verifier
Validates Kubernetes manifests against Gateway API v1.2 JSON schemas to detect missing ReferenceGrant resources and malformed backendRefs.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kubernetes Gateway API v1.2 Cross-Namespace Mutual TLS and ReferenceGrant Routing Boundaries

Kubernetes Gateway API v1.2 Cross-Namespace Mutual TLS and ReferenceGrant Routing Boundaries defines an industrial-grade behavioral standard for devops engineering. Enforces strict cryptographically verified ReferenceGrant access boundaries for cross-namespace routing and mutual TLS handshakes under Kubernetes Gateway API v1.2 specifications. In multi-tenant clusters, Gateway resources and downstream HTTPRoute/BackendTLSPolicy objects spanning namespace perimeters must bind exclusively through explicit, bi-directional ReferenceGrant contracts to preclude route hijacking and certificate spoofing. Failure to declare granular TargetRef/From contracts breaches tenant network isolation and exposes backend mesh endpoints to cross-namespace traffic interception. 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: Implicit Cross-Namespace Route Attachment and Unbounded BackendTLSPolicy Delegation Without Explicit ReferenceGrant Enforcement 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 DriftImplicit Cross-Namespace Route Attachment and Unbounded BackendTLSPolicy Delegation Without Explicit ReferenceGrant EnforcementCritical
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 deploy a gateway.networking.k8s.io/v1beta1 ReferenceGrant in the target namespace whenever an HTTPRoute in namespace A references a Service or Secret in namespace B, or when a Gateway in namespace A binds Routes in namespace B.

Engineers MUST ALWAYS deploy a gateway.networking.k8s.io/v1beta1 ReferenceGrant in the target namespace whenever an HTTPRoute in namespace A references a Service or Secret in namespace B, or when a Gateway in namespace A binds Routes in namespace B.

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 'allowedRoutes.namespaces.from

Engineers MUST NOT configure 'allowedRoutes.namespaces.from: All' on Gateway listeners without strict ReferenceGrant constraints and specific route selector labels.

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

Services accessed across namespace boundaries under mTLS MUST bind a BackendTLSPolicy declaring an explicit ConfigMap/Secret CA certificate reference and strict hostname validation matching the SAN in the backend certificate.

Services accessed across namespace boundaries under mTLS MUST bind a BackendTLSPolicy declaring an explicit ConfigMap/Secret CA certificate reference and strict hostname validation matching the SAN in the backend certificate.

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

ReferenceGrant definitions MUST restrict the 'from' stanza to exact Resource kinds ('HTTPRoute', 'Gateway') and exact originating namespaces, NEVER using wildcards or unconstrained scope.

ReferenceGrant definitions MUST restrict the 'from' stanza to exact Resource kinds ('HTTPRoute', 'Gateway') and exact originating namespaces, NEVER using wildcards or unconstrained scope.

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

Engineers MUST NEVER permit cross-namespace Secret references for Gateway TLS listener termination unless a ReferenceGrant explicitly permits the Gateway kind in the certificate authority's target namespace.

Engineers MUST NEVER permit cross-namespace Secret references for Gateway TLS listener termination unless a ReferenceGrant explicitly permits the Gateway kind in the certificate authority's target namespace.

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 v1.2 Cross-Namespace Mutual TLS and ReferenceGrant Routing Boundaries critical for AI coding assistants?

Enforces strict cryptographically verified ReferenceGrant access boundaries for cross-namespace routing and mutual TLS handshakes under Kubernetes Gateway API v1.2 specifications. In multi-tenant clusters, Gateway resources and downstream HTTPRoute/BackendTLSPolicy objects spanning namespace perimeters must bind exclusively through explicit, bi-directional ReferenceGrant contracts to preclude route hijacking and certificate spoofing. Failure to declare granular TargetRef/From contracts breaches tenant network isolation and exposes backend mesh endpoints to cross-namespace traffic interception. 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 (Implicit Cross-Namespace Route Attachment and Unbounded BackendTLSPolicy Delegation Without Explicit ReferenceGrant Enforcement) 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