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

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

Enforces strict tenant isolation across Kubernetes namespaces by mandating explicit ReferenceGrant validation before any cross-namespace HTTPRoute parentRef or backendRef is compiled into Envoy xDS configuration. Prevents unauthorized traffic interception, route hijacking, and backend exposure in multi-tenant clusters by ensuring unverified cross-namespace references evaluate to a terminal RefNotPermitted status.

Prohibited Anti-Pattern: Compiling Cross-Namespace Envoy Route Clusters Without Bidirectional ReferenceGrant Verification

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 tenant isolation across Kubernetes namespaces by mandating explicit ReferenceGrant validation before any cross-namespace HTTPRoute parentRef or backendRef is compiled into Envoy xDS configuration. Prevents unauthorized traffic interception, route hijacking, and backend exposure in multi-tenant clusters by ensuring unverified cross-namespace references evaluate to a terminal RefNotPermitted status.
globs: deploy/**/*.{yaml,yml}, k8s/**/*.{yaml,yml}, charts/**/*.{yaml,yml}, src/controllers/**/*.{ts,go}, src/gateway/**/*.{ts,go}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/k8s-gateway-v1-2-cross-namespace-referencegrant-boundary"
---

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

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Compiling Cross-Namespace Envoy Route Clusters Without Bidirectional ReferenceGrant Verification

## System Constraints
You are a Principal Software Architect and Security Auditor enforcing the Kubernetes Gateway API v1.2 Cross-Namespace Route Inclusion Boundary Standard. You must mandate that every cross-namespace reference (between Gateways, HTTPRoutes, and Service backends) evaluates an explicit, strictly scoped ReferenceGrant resource prior to compiling Envoy xDS filter pipelines, preventing cross-tenant route hijacking.

## Strict Guidelines
- Engineers MUST ALWAYS verify the presence of a matching ReferenceGrant in the target namespace before attaching an HTTPRoute to a Gateway or resolving a cross-namespace Service backendRef.
- Engineers MUST NOT compile Envoy cluster endpoints or RDS routes for backend references that lack a matching ReferenceGrant with exact Group, Kind, and optional Name matching.
- Code MUST set the HTTPRoute condition 'ResolvedRefs' to 'False' with Reason 'RefNotPermitted' immediately upon ReferenceGrant lookup failure or namespace mismatch.
- Services MUST scope ReferenceGrant 'from' fields strictly to authorized namespaces and kinds (e.g., group: gateway.networking.k8s.io, kind: HTTPRoute), rejecting wildcard namespaces ('*') in multi-tenant environments.
- Components NEVER fall back to default namespace sharing or synthesize partial Envoy routes when cross-namespace authorization invariants are unresolved.

## Bad vs Good Implementations
### Envoy Translation Engine: ReferenceGrant Cross-Namespace Verification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Directly compiles cross-namespace backend references into Envoy xDS clusters without querying Kubernetes for an active ReferenceGrant in the destination namespace, violating multi-tenant tenancy boundaries.
```typescript
import { HTTPRoute, EnvoyCluster } from '@k8s/gateway-api';

export function compileRouteToEnvoyCluster(
  route: HTTPRoute,
  backendNamespace: string,
  serviceName: string
): EnvoyCluster {
  // VULNERABILITY: Blindly synthesizes Envoy cluster across namespaces without validating ReferenceGrant.
  // This allows malicious tenants to hijack traffic or route to unauthorized private services.
  return {
    name: `${backendNamespace}_${serviceName}_cluster`,
    type: 'STRICT_DNS',
    connectTimeout: '5s',
    lbPolicy: 'ROUND_ROBIN',
    loadAssignment: {
      clusterName: `${backendNamespace}_${serviceName}_cluster`,
      endpoints: [{ fqdn: `${serviceName}.${backendNamespace}.svc.cluster.local` }]
    }
  };
}
```

#### Production Standard (Correct)
> **Standard**: Validates that cross-namespace backend references strictly match an existing ReferenceGrant in the target namespace before emitting Envoy clusters. Rejects compilation and attaches 'RefNotPermitted' condition on missing or misconfigured grants.
```typescript
import { HTTPRoute, ReferenceGrant, EnvoyCluster, RouteCondition } from '@k8s/gateway-api';

export function compileRouteToEnvoyCluster(
  route: HTTPRoute,
  backendNamespace: string,
  serviceName: string,
  grants: ReferenceGrant[]
): { cluster: EnvoyCluster | null; condition: RouteCondition } {
  const routeNamespace = route.metadata.namespace;

  // In-namespace references do not require a ReferenceGrant
  if (routeNamespace === backendNamespace) {
    return {
      cluster: {
        name: `${backendNamespace}_${serviceName}_cluster`,
        type: 'STRICT_DNS',
        connectTimeout: '5s',
        lbPolicy: 'ROUND_ROBIN',
        loadAssignment: {
          clusterName: `${backendNamespace}_${serviceName}_cluster`,
          endpoints: [{ fqdn: `${serviceName}.${backendNamespace}.svc.cluster.local` }]
        }
      },
      condition: { type: 'ResolvedRefs', status: 'True', reason: 'Resolved' }
    };
  }

  // Mathematically enforce ReferenceGrant boundary in target namespace
  const isAuthorized = grants.some(grant => 
    grant.metadata.namespace === backendNamespace &&
    grant.spec.from.some(f => f.group === 'gateway.networking.k8s.io' && f.kind === 'HTTPRoute' && f.namespace === routeNamespace) &&
    grant.spec.to.some(t => t.group === '' && t.kind === 'Service' && (!t.name || t.name === serviceName))
  );

  if (!isAuthorized) {
    return {
      cluster: null,
      condition: {
        type: 'ResolvedRefs',
        status: 'False',
        reason: 'RefNotPermitted',
        message: `Cross-namespace reference from ${routeNamespace} to Service ${backendNamespace}/${serviceName} denied by boundary policy`
      }
    };
  }

  return {
    cluster: {
      name: `${backendNamespace}_${serviceName}_cluster`,
      type: 'STRICT_DNS',
      connectTimeout: '5s',
      lbPolicy: 'ROUND_ROBIN',
      loadAssignment: {
        clusterName: `${backendNamespace}_${serviceName}_cluster`,
        endpoints: [{ fqdn: `${serviceName}.${backendNamespace}.svc.cluster.local` }]
      }
    },
    condition: { type: 'ResolvedRefs', status: 'True', reason: 'Resolved' }
  };
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector
Inspects cluster state, Gateway API CRDs, HTTPRoutes, and ReferenceGrants to audit cross-namespace policies.
Recommended Agent Skills (askills.dev)

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

Kubeconform Gateway Validator
Validates Gateway API v1.2 manifests against official JSON schemas including ReferenceGrant specifications.
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 tenant isolation across Kubernetes namespaces by mandating explicit ReferenceGrant validation before any cross-namespace HTTPRoute parentRef or backendRef is compiled into Envoy xDS configuration. Prevents unauthorized traffic interception, route hijacking, and backend exposure in multi-tenant clusters by ensuring unverified cross-namespace references evaluate to a terminal RefNotPermitted status. 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: Compiling Cross-Namespace Envoy Route Clusters Without Bidirectional ReferenceGrant Verification 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 DriftCompiling Cross-Namespace Envoy Route Clusters Without Bidirectional ReferenceGrant VerificationCritical
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 verify the presence of a matching ReferenceGrant in the target namespace before attaching an HTTPRoute to a Gateway or resolving a cross-namespace Service backendRef.

Engineers MUST ALWAYS verify the presence of a matching ReferenceGrant in the target namespace before attaching an HTTPRoute to a Gateway or resolving a cross-namespace Service backendRef.

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 compile Envoy cluster endpoints or RDS routes for backend references that lack a matching ReferenceGrant with exact Group, Kind, and optional Name matching.

Engineers MUST NOT compile Envoy cluster endpoints or RDS routes for backend references that lack a matching ReferenceGrant with exact Group, Kind, and optional Name matching.

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

Code MUST set the HTTPRoute condition 'ResolvedRefs' to 'False' with Reason 'RefNotPermitted' immediately upon ReferenceGrant lookup failure or namespace mismatch.

Code MUST set the HTTPRoute condition 'ResolvedRefs' to 'False' with Reason 'RefNotPermitted' immediately upon ReferenceGrant lookup failure or namespace mismatch.

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 scope ReferenceGrant 'from' fields strictly to authorized namespaces and kinds (e.g., group

Services MUST scope ReferenceGrant 'from' fields strictly to authorized namespaces and kinds (e.g., group: gateway.networking.k8s.io, kind: HTTPRoute), rejecting wildcard namespaces ('*') in multi-tenant 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.
5

Components NEVER fall back to default namespace sharing or synthesize partial Envoy routes when cross-namespace authorization invariants are unresolved.

Components NEVER fall back to default namespace sharing or synthesize partial Envoy routes when cross-namespace authorization invariants are unresolved.

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 tenant isolation across Kubernetes namespaces by mandating explicit ReferenceGrant validation before any cross-namespace HTTPRoute parentRef or backendRef is compiled into Envoy xDS configuration. Prevents unauthorized traffic interception, route hijacking, and backend exposure in multi-tenant clusters by ensuring unverified cross-namespace references evaluate to a terminal RefNotPermitted status. 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 (Compiling Cross-Namespace Envoy Route Clusters Without Bidirectional ReferenceGrant Verification) 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