Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets | AgentRules.org

Rules Stacks Clients Auditor Pruner Self-Heal RFCs Benchmark CLI CI/CD Authors Submit

This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →

devopscritical PriorityID: k8s-gateway-api-referencegrant-cross-namespace-invariant

Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets

Enforces mandatory, least-privilege ReferenceGrant declarations in target namespaces whenever Gateway API resources traverse namespace boundaries. Prevents cross-namespace route hijacking, service impersonation, and unauthorized TLS certificate exfiltration across multi-tenant Kubernetes clusters.

Prohibited Anti-Pattern: Attaching Cross-Namespace Routes or TLS Secrets Without an Explicit, Scoped ReferenceGrant

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets - Enforces mandatory, least-privilege ReferenceGrant declarations in target namespaces whenever Gateway API resources traverse namespace boundaries. Prevents cross-namespace route hijacking, service impersonation, and unauthorized TLS certificate exfiltration across multi-tenant Kubernetes clusters.
globs: k8s/**/*.yaml, deploy/**/*.yaml, manifests/**/*.yaml, helm/**/*.yaml, infra/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/k8s-gateway-api-referencegrant-cross-namespace-invariant"
---

# Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Attaching Cross-Namespace Routes or TLS Secrets Without an Explicit, Scoped ReferenceGrant

## System Constraints
You are a Principal Cloud Native Infrastructure Architect and Network Security Auditor enforcing Kubernetes Gateway API specifications (v1/v1beta1). You MUST reject any cross-namespace parentRef, backendRef, or certificateRef that lacks an explicit, co-located ReferenceGrant in the referenced resource's namespace. Disallow wildcard permissions and enforce least-privilege administrative delegation.

## Strict Guidelines
- Target namespaces hosting referenced Services, Gateways, or Secrets MUST define an explicit `gateway.networking.k8s.io/v1beta1` ReferenceGrant before foreign namespaces can bind to them.
- Engineers MUST NOT rely on implicit trust or assume controllers will permit cross-namespace `parentRefs` or `backendRefs` without an active ReferenceGrant.
- ReferenceGrant resources MUST NEVER specify wildcard (`*`) values for `from[].namespace`, `from[].kind`, or `to[].kind`.
- Gateways referencing TLS Secret resources residing in foreign namespaces MUST have explicit ReferenceGrants with `to[].group: ""` and `to[].kind: Secret` located inside the secret's namespace.
- HTTPRoute manifests referencing cross-namespace Service backends MUST restrict `to[].name` within the target ReferenceGrant whenever individual service isolation is required.
- CI/CD deployment pipelines MUST validate that Gateway API resources with cross-namespace references deploy atomically with their corresponding ReferenceGrant resources.

## Bad vs Good Implementations
### Cross-Namespace Backend Routing Protection

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Cross-namespace backend reference from 'tenant-a' to 'shared-services' without a corresponding ReferenceGrant in 'shared-services'. The Gateway controller will reject the route, and leaving access unmanaged risks unauthorized route injection.
```yaml
# ANTI-PATTERN: HTTPRoute in tenant-a references a Service in shared-services without a ReferenceGrant
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-a-api
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: shared-infra
  rules:
    - backendRefs:
        - name: shared-auth-service
          namespace: shared-services # Rejected by Gateway API controller; causes silent route drop
          port: 8080
```

#### Production Standard (Correct)
> **Standard**: The ReferenceGrant deployed in 'shared-services' explicitly delegates read/forwarding access to HTTPRoute objects residing strictly in 'tenant-a' for the specific 'shared-auth-service' resource.
```yaml
# PRODUCTION FIX: Target namespace explicitly authorizes tenant-a via ReferenceGrant
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-tenant-a-auth-access
  namespace: shared-services
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: tenant-a
  to:
    - group: ""
      kind: Service
      name: shared-auth-service
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-a-api
  namespace: tenant-a
spec:
  parentRefs:
    - name: shared-gateway
      namespace: shared-infra
  rules:
    - backendRefs:
        - name: shared-auth-service
          namespace: shared-services
          port: 8080
```

Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector MCP

Validates live Kubernetes Gateway API resources, CRD versions, and ReferenceGrant authorization bindings.

Recommended Agent Skills (askills.dev)

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

Validates Kubernetes Gateway API v1/v1beta1 schemas and custom resource constraints during pre-commit and CI stages.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets

Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets defines an industrial-grade behavioral standard for devops engineering. Enforces mandatory, least-privilege ReferenceGrant declarations in target namespaces whenever Gateway API resources traverse namespace boundaries. Prevents cross-namespace route hijacking, service impersonation, and unauthorized TLS certificate exfiltration across multi-tenant Kubernetes clusters. 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: Attaching Cross-Namespace Routes or TLS Secrets Without an Explicit, Scoped ReferenceGrant 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Attaching Cross-Namespace Routes or TLS Secrets Without an Explicit, Scoped ReferenceGrant	Critical	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 Inconsistency	AI 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

Target namespaces hosting referenced Services, Gateways, or Secrets MUST define an explicit `gateway.networking.k8s.io/v1beta1` ReferenceGrant before foreign namespaces can bind to them.

Target namespaces hosting referenced Services, Gateways, or Secrets MUST define an explicit `gateway.networking.k8s.io/v1beta1` ReferenceGrant before foreign namespaces can bind to them.

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 rely on implicit trust or assume controllers will permit cross-namespace `parentRefs` or `backendRefs` without an active ReferenceGrant.

Engineers MUST NOT rely on implicit trust or assume controllers will permit cross-namespace `parentRefs` or `backendRefs` without 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.

3

ReferenceGrant resources MUST NEVER specify wildcard (`*`) values for `from[].namespace`, `from[].kind`, or `to[].kind`.

ReferenceGrant resources MUST NEVER specify wildcard (`*`) values for `from[].namespace`, `from[].kind`, or `to[].kind`.

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

Gateways referencing TLS Secret resources residing in foreign namespaces MUST have explicit ReferenceGrants with `to[].group

Gateways referencing TLS Secret resources residing in foreign namespaces MUST have explicit ReferenceGrants with `to[].group: ""` and `to[].kind: Secret` located inside the secret's 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.

5

HTTPRoute manifests referencing cross-namespace Service backends MUST restrict `to[].name` within the target ReferenceGrant whenever individual service isolation is required.

HTTPRoute manifests referencing cross-namespace Service backends MUST restrict `to[].name` within the target ReferenceGrant whenever individual service isolation is required.

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.

6

CI/CD deployment pipelines MUST validate that Gateway API resources with cross-namespace references deploy atomically with their corresponding ReferenceGrant resources.

CI/CD deployment pipelines MUST validate that Gateway API resources with cross-namespace references deploy atomically with their corresponding ReferenceGrant resources.

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 Mandatory ReferenceGrant for Cross-Namespace Gateway API Resources and TLS Secrets critical for AI coding assistants?

Enforces mandatory, least-privilege ReferenceGrant declarations in target namespaces whenever Gateway API resources traverse namespace boundaries. Prevents cross-namespace route hijacking, service impersonation, and unauthorized TLS certificate exfiltration across multi-tenant Kubernetes clusters. 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 (Attaching Cross-Namespace Routes or TLS Secrets Without an Explicit, Scoped ReferenceGrant) 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 →

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.

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.

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

Mandatory