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-reference-grant-cross-namespace-invariant

Gateway API v1.2 ReferenceGrant Bidirectional Cross-Namespace Invariant

Enforces strict bidirectional trust handshakes across Kubernetes namespaces in Gateway API v1.2 deployments using scoped ReferenceGrant resources. Prevents cross-tenant traffic hijacking and unauthorized service attachment by ensuring every cross-namespace HTTPRoute-to-Service and Gateway-to-Secret binding contains a corresponding, non-wildcarded ReferenceGrant in the target namespace.

Prohibited Anti-Pattern: Unauthenticated Cross-Namespace Backend Routing Without Target-Side ReferenceGrant Handshakes

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Gateway API v1.2 ReferenceGrant Bidirectional Cross-Namespace Invariant - Enforces strict bidirectional trust handshakes across Kubernetes namespaces in Gateway API v1.2 deployments using scoped ReferenceGrant resources. Prevents cross-tenant traffic hijacking and unauthorized service attachment by ensuring every cross-namespace HTTPRoute-to-Service and Gateway-to-Secret binding contains a corresponding, non-wildcarded ReferenceGrant in the target namespace.
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-reference-grant-cross-namespace-invariant"
---

# Gateway API v1.2 ReferenceGrant Bidirectional Cross-Namespace Invariant

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unauthenticated Cross-Namespace Backend Routing Without Target-Side ReferenceGrant Handshakes

## System Constraints
You are a Principal Infrastructure and Security Architect enforcing the Kubernetes Gateway API v1.2 ReferenceGrant cross-namespace routing invariant. You must reject any cross-namespace route or gateway binding that lacks an explicit, target-scoped ReferenceGrant in the destination namespace. Enforce bidirectional cryptographic and programmatic handshakes across namespace boundaries to eliminate multi-tenant ingress hijack vulnerabilities.

## Strict Guidelines
- Engineers MUST ALWAYS create an explicit ReferenceGrant in the target namespace whenever an HTTPRoute references a Service or a Gateway references a Secret across namespace boundaries.
- Engineers MUST NOT deploy wildcard (spec.to[].name: '*') ReferenceGrants in shared or multi-tenant production namespaces.
- HTTPRoute backendRefs targeting external namespaces MUST explicitly define the 'namespace' field alongside 'name', 'group', and 'port'.
- Gateway listeners MUST restrict route attachment using 'allowedRoutes.namespaces.from: Selector' or 'Same', rejecting unconstrained 'All' policies across trust domains.
- Services referenced across namespaces MUST verify that the ReferenceGrant spec.from accurately matches the client namespace and resource kind (e.g., group: gateway.networking.k8s.io, kind: HTTPRoute).

## Bad vs Good Implementations
### Cross-Namespace Backend Reference Security Boundary

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The HTTPRoute attempts to reference a Service in 'tenant-b' without an explicit ReferenceGrant deployed inside 'tenant-b'. This triggers a ResolvedRefs: RefNotPermitted failure in compliant Gateway API v1.2 controllers and presents a high-risk misconfiguration pattern.
```yaml
# INSECURE: tenant-a attempts to route cross-namespace to tenant-b without a ReferenceGrant
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: billing-proxy
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: ingress-infra
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /billing
      backendRefs:
        - name: payment-service
          namespace: tenant-b # Cross-namespace reference rejected by controller (ResolvedRefs: False)
          port: 8080
```

#### Production Standard (Correct)
> **Standard**: The target namespace 'tenant-b' provisions a ReferenceGrant explicitly authorizing HTTPRoutes originating from 'tenant-a' to bind to 'payment-service'. This completes the bidirectional handshake required by Gateway API v1.2 specification.
```yaml
# SECURE: tenant-a references tenant-b Service authorized by an explicit ReferenceGrant
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: billing-proxy
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: ingress-infra
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /billing
      backendRefs:
        - group: ""
          kind: Service
          name: payment-service
          namespace: tenant-b
          port: 8080
---
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-tenant-a-billing
  namespace: tenant-b
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: tenant-a
  to:
    - group: ""
      kind: Service
      name: payment-service
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector
Verifies live ReferenceGrant CRDs, Gateway status conditions, and ResolvedRefs states across namespaces.
Recommended Agent Skills (askills.dev)

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

Kubeconform Gateway API Validator
Validates Kubernetes Gateway API v1.2 resource schemas and validates cross-namespace ReferenceGrant linkage in CI/CD.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Gateway API v1.2 ReferenceGrant Bidirectional Cross-Namespace Invariant

Gateway API v1.2 ReferenceGrant Bidirectional Cross-Namespace Invariant defines an industrial-grade behavioral standard for devops engineering. Enforces strict bidirectional trust handshakes across Kubernetes namespaces in Gateway API v1.2 deployments using scoped ReferenceGrant resources. Prevents cross-tenant traffic hijacking and unauthorized service attachment by ensuring every cross-namespace HTTPRoute-to-Service and Gateway-to-Secret binding contains a corresponding, non-wildcarded ReferenceGrant in the target namespace. 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: Unauthenticated Cross-Namespace Backend Routing Without Target-Side ReferenceGrant Handshakes 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 DriftUnauthenticated Cross-Namespace Backend Routing Without Target-Side ReferenceGrant HandshakesCritical
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 create an explicit ReferenceGrant in the target namespace whenever an HTTPRoute references a Service or a Gateway references a Secret across namespace boundaries.

Engineers MUST ALWAYS create an explicit ReferenceGrant in the target namespace whenever an HTTPRoute references a Service or a Gateway references a Secret across namespace boundaries.

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 deploy wildcard (spec.to[].name

Engineers MUST NOT deploy wildcard (spec.to[].name: '*') ReferenceGrants in shared or multi-tenant production 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.
3

HTTPRoute backendRefs targeting external namespaces MUST explicitly define the 'namespace' field alongside 'name', 'group', and 'port'.

HTTPRoute backendRefs targeting external namespaces MUST explicitly define the 'namespace' field alongside 'name', 'group', and 'port'.

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

Gateway listeners MUST restrict route attachment using 'allowedRoutes.namespaces.from

Gateway listeners MUST restrict route attachment using 'allowedRoutes.namespaces.from: Selector' or 'Same', rejecting unconstrained 'All' policies across trust domains.

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

Services referenced across namespaces MUST verify that the ReferenceGrant spec.from accurately matches the client namespace and resource kind (e.g., group

Services referenced across namespaces MUST verify that the ReferenceGrant spec.from accurately matches the client namespace and resource kind (e.g., group: gateway.networking.k8s.io, kind: HTTPRoute).

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 Gateway API v1.2 ReferenceGrant Bidirectional Cross-Namespace Invariant critical for AI coding assistants?

Enforces strict bidirectional trust handshakes across Kubernetes namespaces in Gateway API v1.2 deployments using scoped ReferenceGrant resources. Prevents cross-tenant traffic hijacking and unauthorized service attachment by ensuring every cross-namespace HTTPRoute-to-Service and Gateway-to-Secret binding contains a corresponding, non-wildcarded ReferenceGrant in the target namespace. 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 (Unauthenticated Cross-Namespace Backend Routing Without Target-Side ReferenceGrant Handshakes) 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

Gateway