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-referencegrant-boundary-standard-kubernetes-gatew-959

Kubernetes Gateway API v1.2 Cross-Namespace ReferenceGrant Boundary Standard

Enforces strict authorization boundaries for cross-namespace routing within Kubernetes Gateway API v1.2 environments. Requires explicit ReferenceGrant resources in target service namespaces before HTTPRoute or GRPCRoute objects can reference backend services across namespace boundaries. Prevents multi-tenant traffic hijacking and unintended blast-radius expansion across shared ingress gateways and service meshes.

Prohibited Anti-Pattern: Cross-Namespace Backend Hijacking Without Explicit ReferenceGrant Consent

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kubernetes Gateway API v1.2 Cross-Namespace ReferenceGrant Boundary Standard - Enforces strict authorization boundaries for cross-namespace routing within Kubernetes Gateway API v1.2 environments. Requires explicit ReferenceGrant resources in target service namespaces before HTTPRoute or GRPCRoute objects can reference backend services across namespace boundaries. Prevents multi-tenant traffic hijacking and unintended blast-radius expansion across shared ingress gateways and service meshes.
globs: **/*.yaml, **/*.yml, helm/**/*.yaml, kustomize/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/k8s-gateway-api-referencegrant-boundary-standard-kubernetes-gatew-959"
---

# Kubernetes Gateway API v1.2 Cross-Namespace ReferenceGrant Boundary Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Cross-Namespace Backend Hijacking Without Explicit ReferenceGrant Consent

## System Constraints
You are a Principal Platform and Security Architect enforcing Kubernetes Gateway API v1.2 cross-namespace trust invariants. Your task is to mandate that any HTTPRoute, GRPCRoute, or Gateway cross-namespace reference to backends or secrets is paired with an explicit, least-privilege ReferenceGrant in the destination namespace. Never permit cross-namespace route-to-backend references without a corresponding ReferenceGrant manifest.

## Strict Guidelines
- Engineers MUST ALWAYS create a ReferenceGrant in the target/backend namespace whenever an HTTPRoute or GRPCRoute in a different namespace references a Service or backend in that target namespace.
- Engineers MUST NOT use wildcard ('*') group or kind selectors within ReferenceGrant 'from' or 'to' blocks in production multi-tenant clusters.
- Engineers MUST explicitly restrict the 'from' namespace in ReferenceGrant resources to the precise source namespace operating the routing resource.
- Gateway implementations MUST drop or mark routes as invalid with 'ResolvedRefs: False' and Reason 'RefNotPermitted' when cross-namespace targets lack an active ReferenceGrant.
- Platform operators SHOULD enforce OPA Gatekeeper or Kyverno policies that reject Route manifests referencing foreign namespaces lacking a corresponding ReferenceGrant.

## Bad vs Good Implementations
### Cross-Namespace HTTPRoute Backend Reference Without vs With ReferenceGrant

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The HTTPRoute in namespace 'tenant-a' attempts to route external traffic to 'billing-svc' located in 'tenant-b'. Without an explicit ReferenceGrant deployed inside 'tenant-b', this configuration either triggers silent routing drops or permits unauthenticated cross-tenant traffic hijacking if the gateway controller is misconfigured.
```yaml
# Tenant Route attempting cross-namespace bind without target consent
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-route
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: ingress-infra
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /api/v1/billing
      backendRefs:
        # CRITICAL VULNERABILITY: References service in tenant-b without ReferenceGrant
        - name: billing-svc
          namespace: tenant-b
          port: 8080
```

#### Production Standard (Correct)
> **Standard**: Tenant B explicitly defines a ReferenceGrant in its own namespace, declaring that HTTPRoute resources from namespace 'tenant-a' are strictly authorized to reference 'billing-svc'. This adheres to Kubernetes Gateway API boundary standards and maintains multi-tenant isolation.
```yaml
# 1. Explicit ReferenceGrant inside the target backend namespace
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-tenant-a-billing-access
  namespace: tenant-b
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: tenant-a
  to:
    - group: ""
      kind: Service
      name: billing-svc
---
# 2. Authorized HTTPRoute in the source namespace
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-route
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: ingress-infra
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /api/v1/billing
      backendRefs:
        - name: billing-svc
          namespace: tenant-b
          port: 8080
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Inspector MCP
Enables inspection and schema validation of deployed Gateway API and ReferenceGrant resources in live clusters.
Recommended Agent Skills (askills.dev)

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

Kubeconform Gateway API Validator
Validates Kubernetes manifests against Gateway API v1.2 JSON schemas to detect missing or malformed ReferenceGrant definitions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kubernetes Gateway API v1.2 Cross-Namespace ReferenceGrant Boundary Standard

Kubernetes Gateway API v1.2 Cross-Namespace ReferenceGrant Boundary Standard defines an industrial-grade behavioral standard for devops engineering. Enforces strict authorization boundaries for cross-namespace routing within Kubernetes Gateway API v1.2 environments. Requires explicit ReferenceGrant resources in target service namespaces before HTTPRoute or GRPCRoute objects can reference backend services across namespace boundaries. Prevents multi-tenant traffic hijacking and unintended blast-radius expansion across shared ingress gateways and service meshes. 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: Cross-Namespace Backend Hijacking Without Explicit ReferenceGrant Consent 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 DriftCross-Namespace Backend Hijacking Without Explicit ReferenceGrant ConsentCritical
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 a ReferenceGrant in the target/backend namespace whenever an HTTPRoute or GRPCRoute in a different namespace references a Service or backend in that target namespace.

Engineers MUST ALWAYS create a ReferenceGrant in the target/backend namespace whenever an HTTPRoute or GRPCRoute in a different namespace references a Service or backend in that 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.
2

Engineers MUST NOT use wildcard ('*') group or kind selectors within ReferenceGrant 'from' or 'to' blocks in production multi-tenant clusters.

Engineers MUST NOT use wildcard ('*') group or kind selectors within ReferenceGrant 'from' or 'to' blocks in production multi-tenant clusters.

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 explicitly restrict the 'from' namespace in ReferenceGrant resources to the precise source namespace operating the routing resource.

Engineers MUST explicitly restrict the 'from' namespace in ReferenceGrant resources to the precise source namespace operating the routing resource.

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 implementations MUST drop or mark routes as invalid with 'ResolvedRefs

Gateway implementations MUST drop or mark routes as invalid with 'ResolvedRefs: False' and Reason 'RefNotPermitted' when cross-namespace targets lack an active ReferenceGrant.

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

Platform operators SHOULD enforce OPA Gatekeeper or Kyverno policies that reject Route manifests referencing foreign namespaces lacking a corresponding ReferenceGrant.

Platform operators SHOULD enforce OPA Gatekeeper or Kyverno policies that reject Route manifests referencing foreign namespaces lacking a corresponding ReferenceGrant.

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 ReferenceGrant Boundary Standard critical for AI coding assistants?

Enforces strict authorization boundaries for cross-namespace routing within Kubernetes Gateway API v1.2 environments. Requires explicit ReferenceGrant resources in target service namespaces before HTTPRoute or GRPCRoute objects can reference backend services across namespace boundaries. Prevents multi-tenant traffic hijacking and unintended blast-radius expansion across shared ingress gateways and service meshes. 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 (Cross-Namespace Backend Hijacking Without Explicit ReferenceGrant Consent) 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