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: kubernetes-gateway-api-referencegrant-boundary

Kubernetes Gateway API Cross-Namespace ReferenceGrant Security Boundary Enforcement

Cross-namespace references in Kubernetes Gateway API—such as Routes forwarding to Services or Gateways referencing TLS Secrets across namespace boundaries—expose multi-tenant clusters to unauthorized traffic interception, credential exfiltration, and route hijacking. All cross-namespace linkages must be explicitly authorized using bidirectional ReferenceGrant resources scoped to specific namespaces and kinds without wildcard permissions.

Prohibited Anti-Pattern: Implicit Cross-Namespace Route Hijacking or Wildcarded ReferenceGrant Exploitation

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kubernetes Gateway API Cross-Namespace ReferenceGrant Security Boundary Enforcement - Cross-namespace references in Kubernetes Gateway API—such as Routes forwarding to Services or Gateways referencing TLS Secrets across namespace boundaries—expose multi-tenant clusters to unauthorized traffic interception, credential exfiltration, and route hijacking. All cross-namespace linkages must be explicitly authorized using bidirectional ReferenceGrant resources scoped to specific namespaces and kinds without wildcard permissions.
globs: **/*.yaml, **/*.yml, **/k8s/**, **/helm/**, **/kustomize/**, **/manifests/**
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/kubernetes-gateway-api-referencegrant-boundary"
---

# Kubernetes Gateway API Cross-Namespace ReferenceGrant Security Boundary Enforcement

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Implicit Cross-Namespace Route Hijacking or Wildcarded ReferenceGrant Exploitation

## System Constraints
You are a Principal Infrastructure & Platform Security Engineer enforcing strict boundary isolation for Kubernetes Gateway API resources. Mandate explicit, cryptographically verifiable, and resource-level authorization handshakes via ReferenceGrant (gateway.networking.k8s.io/v1beta1). Prohibit unconstrained cross-namespace Route-to-Service linkages, unauthorized Gateway-to-Secret TLS attachments, and wildcard namespace declarations in multi-tenant environments.

## Strict Guidelines
- Engineers MUST ALWAYS create a ReferenceGrant in the destination namespace whenever a Route (HTTPRoute/GRPCRoute/TCPRoute) or Gateway references a Service or Secret across a namespace boundary.
- Engineers MUST NOT specify wildcard values (`*`) in `from[].namespace` or leave `to[].name` unconstrained within multi-tenant ReferenceGrant manifests.
- Manifests MUST explicitly declare exact source resource metadata (`group: gateway.networking.k8s.io`, `kind: HTTPRoute`) and target resource constraints (`group: ''`, `kind: Service`).
- GitOps and CI pipelines MUST assert that HTTPRoute status conditions evaluate `ResolvedRefs: True` and immediately flag `RefNotPermitted` violations as deployment blockers.
- Gateway TLS listener configurations MUST NEVER bind cross-namespace TLS certificates without a dedicated ReferenceGrant targeting Secret kinds strictly restricted to the Gateway namespace.

## Bad vs Good Implementations
### Cross-Namespace BackendRef Authorization via Explicit ReferenceGrant

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: tenant-a declares an HTTPRoute directing traffic to core-billing-service in tenant-b. Without a ReferenceGrant deployed within tenant-b explicitly permitting tenant-a to route to its Service, this creates an unauthorized routing condition. Relying on permissive or missing grant admission allows malicious tenants to intercept internal routing topologies.
```yaml
# INSECURE: Tenant-A attempts to hijack traffic destined for Tenant-B's internal billing service.
# In clusters without strict admission or missing ReferenceGrants, this risks silent misrouting or controller crash loops.
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: billing-intercept-route
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: ingress-gateway
  hostnames:
    - "billing.corp.internal"
  rules:
    - backendRefs:
        - name: core-billing-service
          namespace: tenant-b # Cross-namespace reference WITHOUT valid grant handshake in tenant-b
          port: 8443
```

#### Production Standard (Correct)
> **Standard**: tenant-b controls its own trust domain by hosting the ReferenceGrant. The grant explicitly permits only HTTPRoute resources residing strictly in tenant-a to target core-billing-service, adhering to the principle of least privilege and fulfilling the Gateway API security contract.
```yaml
# SECURE: Target namespace (tenant-b) explicitly authorizes tenant-a's HTTPRoute via ReferenceGrant.
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-tenant-a-billing-routing
  namespace: tenant-b
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: tenant-a
  to:
    - group: ""
      kind: Service
      name: core-billing-service
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: authorized-billing-route
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: ingress-gateway
  hostnames:
    - "billing.corp.internal"
  rules:
    - backendRefs:
        - name: core-billing-service
          namespace: tenant-b
          port: 8443
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector MCP
Inspects active Gateway API resources, validates Route conditions (ResolvedRefs), and enforces namespace boundary audits.
Recommended Agent Skills (askills.dev)

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

Gateway API Schema & Policy Validator
Validates Kubernetes Gateway API custom resource schemas and rejects invalid ReferenceGrant configurations prior to GitOps commit.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kubernetes Gateway API Cross-Namespace ReferenceGrant Security Boundary Enforcement

Kubernetes Gateway API Cross-Namespace ReferenceGrant Security Boundary Enforcement defines an industrial-grade behavioral standard for devops engineering. Cross-namespace references in Kubernetes Gateway API—such as Routes forwarding to Services or Gateways referencing TLS Secrets across namespace boundaries—expose multi-tenant clusters to unauthorized traffic interception, credential exfiltration, and route hijacking. All cross-namespace linkages must be explicitly authorized using bidirectional ReferenceGrant resources scoped to specific namespaces and kinds without wildcard permissions. 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 Hijacking or Wildcarded ReferenceGrant Exploitation 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 Hijacking or Wildcarded ReferenceGrant ExploitationCritical
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 destination namespace whenever a Route (HTTPRoute/GRPCRoute/TCPRoute) or Gateway references a Service or Secret across a namespace boundary.

Engineers MUST ALWAYS create a ReferenceGrant in the destination namespace whenever a Route (HTTPRoute/GRPCRoute/TCPRoute) or Gateway references a Service or Secret across a namespace boundary.

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 specify wildcard values (`*`) in `from[].namespace` or leave `to[].name` unconstrained within multi-tenant ReferenceGrant manifests.

Engineers MUST NOT specify wildcard values (`*`) in `from[].namespace` or leave `to[].name` unconstrained within multi-tenant ReferenceGrant manifests.

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

Manifests MUST explicitly declare exact source resource metadata (`group

Manifests MUST explicitly declare exact source resource metadata (`group: gateway.networking.k8s.io`, `kind: HTTPRoute`) and target resource constraints (`group: ''`, `kind: Service`).

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

GitOps and CI pipelines MUST assert that HTTPRoute status conditions evaluate `ResolvedRefs

GitOps and CI pipelines MUST assert that HTTPRoute status conditions evaluate `ResolvedRefs: True` and immediately flag `RefNotPermitted` violations as deployment blockers.

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

Gateway TLS listener configurations MUST NEVER bind cross-namespace TLS certificates without a dedicated ReferenceGrant targeting Secret kinds strictly restricted to the Gateway namespace.

Gateway TLS listener configurations MUST NEVER bind cross-namespace TLS certificates without a dedicated ReferenceGrant targeting Secret kinds strictly restricted to the Gateway 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 Cross-Namespace ReferenceGrant Security Boundary Enforcement critical for AI coding assistants?

Cross-namespace references in Kubernetes Gateway API—such as Routes forwarding to Services or Gateways referencing TLS Secrets across namespace boundaries—expose multi-tenant clusters to unauthorized traffic interception, credential exfiltration, and route hijacking. All cross-namespace linkages must be explicitly authorized using bidirectional ReferenceGrant resources scoped to specific namespaces and kinds without wildcard permissions. 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 Hijacking or Wildcarded ReferenceGrant Exploitation) 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