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-enforcement

Kubernetes Gateway API ReferenceGrant Cross-Namespace Isolation

Enforces strict multi-tenant boundary isolation under the Kubernetes Gateway API specification by mandating explicit ReferenceGrant resources for all cross-namespace references. Prohibits unauthorized cross-namespace backendRefs and parentRefs to prevent traffic hijacking, data exfiltration, and cross-tenant credential or service exposure.

Prohibited Anti-Pattern: Cross-Namespace Service Hijack via Unsanctioned Gateway Route Backends

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kubernetes Gateway API ReferenceGrant Cross-Namespace Isolation - Enforces strict multi-tenant boundary isolation under the Kubernetes Gateway API specification by mandating explicit ReferenceGrant resources for all cross-namespace references. Prohibits unauthorized cross-namespace backendRefs and parentRefs to prevent traffic hijacking, data exfiltration, and cross-tenant credential or service exposure.
globs: **/*.yaml, **/*.yml, **/helm/**/*.yaml, **/templates/**/*.yaml, **/kustomization.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/k8s-gateway-api-referencegrant-enforcement"
---

# Kubernetes Gateway API ReferenceGrant Cross-Namespace Isolation

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Cross-Namespace Service Hijack via Unsanctioned Gateway Route Backends

## System Constraints
You are a Principal Cloud Security and DevOps Architect enforcing Kubernetes Gateway API v1 multi-tenancy invariants. Cross-namespace routing allows tenants to target backend services or gateways across isolation boundaries. You must strictly forbid any cross-namespace reference (such as HTTPRoute backendRef or Secret parentRef) that lacks a co-located, least-privilege ReferenceGrant in the destination namespace. Reject wildcard namespace permissions, catch-all namespace selectors on production Gateways, and missing ReferenceGrant configurations during manifest generation and review.

## Strict Guidelines
- Engineers MUST ALWAYS declare an explicit `ReferenceGrant` in the target namespace when an `HTTPRoute`, `GRPCRoute`, or `TLSRoute` references a `Service` or `Secret` located in a different namespace.
- Engineers MUST NOT use wildcard namespaces (`*`) in `ReferenceGrant.spec.from.namespace` or `Gateway.spec.listeners.allowedRoutes.namespaces.from: All` in shared multi-tenant clusters.
- Code MUST restrict `ReferenceGrant.spec.to` to explicit resource kinds (`Service`, `Secret`) and optionally bind by resource name to prevent broad cross-namespace exposure.
- Services MUST remain non-routable across namespace boundaries unless the owner namespace explicitly authorizes the consumer route's API group, kind, and source namespace via `ReferenceGrant`.
- Components NEVER bind parent Gateway references (`parentRefs`) in restricted infra namespaces without validating that the Gateway listener explicitly permits route attachments from the tenant namespace.

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

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The HTTPRoute attempts to send ingress traffic across tenant boundaries to 'core-billing-svc' in 'core-finance' without an authorizing ReferenceGrant in the 'core-finance' namespace. Conforming Gateway implementations will drop or reject this reference, and non-conforming or misconfigured environments risk unauthorized cross-namespace service hijacking.
```yaml
# INSECURE: Tenant route attaches to a shared core service across namespaces without authorization
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-analytics-route
  namespace: tenant-analytics
spec:
  parentRefs:
    - name: shared-gateway
      namespace: gateway-infra
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /api/v1/billing
      backendRefs:
        - name: core-billing-svc
          namespace: core-finance # Flaw: core-finance has not authorized tenant-analytics
          port: 8080
```

#### Production Standard (Correct)
> **Standard**: A ReferenceGrant is placed directly within the destination namespace ('core-finance') explicitly permitting only 'HTTPRoute' instances from 'tenant-analytics' to bind specifically to 'core-billing-svc'. This adheres to zero-trust multi-tenancy invariants.
```yaml
# SECURE: Target namespace explicitly issues a least-privilege ReferenceGrant
apiVersion: gateway.networking.k8s.io/v1beta1
kind: ReferenceGrant
metadata:
  name: allow-analytics-to-billing
  namespace: core-finance
spec:
  from:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      namespace: tenant-analytics
  to:
    - group: ""
      kind: Service
      name: core-billing-svc
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: tenant-analytics-route
  namespace: tenant-analytics
spec:
  parentRefs:
    - name: shared-gateway
      namespace: gateway-infra
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /api/v1/billing
      backendRefs:
        - name: core-billing-svc
          namespace: core-finance
          port: 8080
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector
Validates live Gateway API custom resource definitions, route attachment statuses, and ReferenceGrant authorization status across namespaces.
Recommended Agent Skills (askills.dev)

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

Kubeconform Policy Validator
Performs static schema and structural validation of Gateway API manifests and ReferenceGrant resources against the official standard schemas.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kubernetes Gateway API ReferenceGrant Cross-Namespace Isolation

Kubernetes Gateway API ReferenceGrant Cross-Namespace Isolation defines an industrial-grade behavioral standard for devops engineering. Enforces strict multi-tenant boundary isolation under the Kubernetes Gateway API specification by mandating explicit ReferenceGrant resources for all cross-namespace references. Prohibits unauthorized cross-namespace backendRefs and parentRefs to prevent traffic hijacking, data exfiltration, and cross-tenant credential or service exposure. 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 Service Hijack via Unsanctioned Gateway Route Backends 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 Service Hijack via Unsanctioned Gateway Route BackendsCritical
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 declare an explicit `ReferenceGrant` in the target namespace when an `HTTPRoute`, `GRPCRoute`, or `TLSRoute` references a `Service` or `Secret` located in a different namespace.

Engineers MUST ALWAYS declare an explicit `ReferenceGrant` in the target namespace when an `HTTPRoute`, `GRPCRoute`, or `TLSRoute` references a `Service` or `Secret` located in a different 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 namespaces (`*`) in `ReferenceGrant.spec.from.namespace` or `Gateway.spec.listeners.allowedRoutes.namespaces.from

Engineers MUST NOT use wildcard namespaces (`*`) in `ReferenceGrant.spec.from.namespace` or `Gateway.spec.listeners.allowedRoutes.namespaces.from: All` in shared 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

Code MUST restrict `ReferenceGrant.spec.to` to explicit resource kinds (`Service`, `Secret`) and optionally bind by resource name to prevent broad cross-namespace exposure.

Code MUST restrict `ReferenceGrant.spec.to` to explicit resource kinds (`Service`, `Secret`) and optionally bind by resource name to prevent broad cross-namespace exposure.

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 remain non-routable across namespace boundaries unless the owner namespace explicitly authorizes the consumer route's API group, kind, and source namespace via `ReferenceGrant`.

Services MUST remain non-routable across namespace boundaries unless the owner namespace explicitly authorizes the consumer route's API group, kind, and source namespace via `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

Components NEVER bind parent Gateway references (`parentRefs`) in restricted infra namespaces without validating that the Gateway listener explicitly permits route attachments from the tenant namespace.

Components NEVER bind parent Gateway references (`parentRefs`) in restricted infra namespaces without validating that the Gateway listener explicitly permits route attachments from the tenant 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 ReferenceGrant Cross-Namespace Isolation critical for AI coding assistants?

Enforces strict multi-tenant boundary isolation under the Kubernetes Gateway API specification by mandating explicit ReferenceGrant resources for all cross-namespace references. Prohibits unauthorized cross-namespace backendRefs and parentRefs to prevent traffic hijacking, data exfiltration, and cross-tenant credential or service exposure. 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 Service Hijack via Unsanctioned Gateway Route Backends) 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