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: spiffe-spire-envoy-sds-rotation-boundary

SPIFFE/SPIRE Workload Identity Envoy SDS Automated Rotation Boundary

Enforces dynamic, zero-downtime X.509 SVID renewal through Envoy Secret Discovery Service (SDS) integrated with the SPIRE Workload API over Unix Domain Sockets. Prevents connection drops, cold restarts, and validation failures under ultra-short TTL (<= 5-minute) rotation boundaries in zero-trust mesh architectures.

Prohibited Anti-Pattern: Mounting static SVID certificates from disk or triggering process restarts upon certificate expiry instead of streaming dynamic Envoy SDS updates.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: SPIFFE/SPIRE Workload Identity Envoy SDS Automated Rotation Boundary - Enforces dynamic, zero-downtime X.509 SVID renewal through Envoy Secret Discovery Service (SDS) integrated with the SPIRE Workload API over Unix Domain Sockets. Prevents connection drops, cold restarts, and validation failures under ultra-short TTL (<= 5-minute) rotation boundaries in zero-trust mesh architectures.
globs: **/envoy/**/*.{yaml,yml,json}, **/spire/**/*.{conf,yaml,yml}, deploy/kubernetes/**/*.{yaml,yml}, helm/**/*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/spiffe-spire-envoy-sds-rotation-boundary"
---

# SPIFFE/SPIRE Workload Identity Envoy SDS Automated Rotation Boundary

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Mounting static SVID certificates from disk or triggering process restarts upon certificate expiry instead of streaming dynamic Envoy SDS updates.

## System Constraints
You are a Principal Infrastructure & Security Architect enforcing strict zero-trust standards via SPIFFE/SPIRE and Envoy SDS. You must reject any static certificate mounts or configurations that trigger sidecar reloads for certificate rotations. All X.509 SVID distribution must stream over Unix Domain Sockets via the SPIRE Workload API into Envoy Secret Discovery Service (SDS) clusters, enforcing SAN pattern matches and seamless active connection preservation under sub-5-minute TTL constraints.

## Strict Guidelines
- Engineers MUST ALWAYS configure Envoy TLS contexts to source X.509 SVIDs and Validation Contexts via Secret Discovery Service (SDS) connected over Unix Domain Sockets (UDS) to the SPIRE Workload API.
- Engineers MUST NOT configure static certificate chains or private keys via file paths ('filename: ...') in transport socket configurations when targeting SPIFFE-managed workloads.
- SDS config sources MUST explicitly define 'api_type: GRPC' with 'transport_api_version: V3' referencing an in-process or local UDS Envoy gRPC cluster connected to SPIRE agent.
- Common TLS contexts MUST enforce strict SPIFFE ID SAN validation using 'match_typed_subject_alt_names' with 'exact' or 'prefix' patterns against the SPIFFE trust domain.
- Services MUST mount the SPIRE Workload API Unix Domain Socket via a dedicated, secure shared volume (such as 'emptyDir: { medium: Memory }' or CSI driver) with restricted POSIX permissions.
- Components NEVER trigger container or pod restarts to rotate expiring certificates; all certificate transitions MUST complete in-memory via SDS streaming without draining non-expired connections.

## Bad vs Good Implementations
### Envoy Static File TLS Mount vs Dynamic SPIRE Workload API SDS Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Static file mounting cannot handle 5-minute X.509 SVID TTLs without constant disk writes and process/container restarts, violating zero-downtime guarantees and risking validation race conditions.
```yaml
# ANTI-PATTERN: Static file mounting causes connection disruption and requires reloads under 5-minute TTLs
transport_socket:
  name: envoy.transport_sockets.tls
  typed_config:
    "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
    common_tls_context:
      tls_certificates:
        - certificate_chain:
            filename: /etc/certs/tls.crt
          private_key:
            filename: /etc/certs/tls.key
      validation_context:
        trusted_ca:
          filename: /etc/certs/ca.crt
```

#### Production Standard (Correct)
> **Standard**: Leverages Envoy's Secret Discovery Service (SDS) pointing to the SPIRE agent gRPC UDS cluster, enabling in-memory streaming rotation of short-lived X.509 SVIDs without connection drops or pod reboots.
```yaml
# PRODUCTION INVARIANT: Dynamic Envoy SDS streaming over SPIRE Agent Workload API Unix Domain Socket
transport_socket:
  name: envoy.transport_sockets.tls
  typed_config:
    "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
    common_tls_context:
      tls_certificate_sds_secret_configs:
        - name: "spiffe://prod.domain/ns/default/sa/payment-svc"
          sds_config:
            api_config_source:
              api_type: GRPC
              transport_api_version: V3
              grpc_services:
                - envoy_grpc:
                    cluster_name: spire_agent
      validation_context_sds_secret_config:
        name: "spiffe://prod.domain"
        sds_config:
          api_config_source:
            api_type: GRPC
            transport_api_version: V3
            grpc_services:
              - envoy_grpc:
                  cluster_name: spire_agent
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Mesh Validator MCP
Inspects and validates live Envoy sidecar configurations, SPIRE Agent CSI driver socket mounts, and dynamic SDS cluster health.
Recommended Agent Skills (askills.dev)

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

SPIRE CLI Inspection Tool
CLI utility for interacting with the local SPIRE agent Workload API socket to inspect attested SVIDs, TTL values, and trust bundles.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: SPIFFE/SPIRE Workload Identity Envoy SDS Automated Rotation Boundary

SPIFFE/SPIRE Workload Identity Envoy SDS Automated Rotation Boundary defines an industrial-grade behavioral standard for devops engineering. Enforces dynamic, zero-downtime X.509 SVID renewal through Envoy Secret Discovery Service (SDS) integrated with the SPIRE Workload API over Unix Domain Sockets. Prevents connection drops, cold restarts, and validation failures under ultra-short TTL (<= 5-minute) rotation boundaries in zero-trust mesh architectures. 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: Mounting static SVID certificates from disk or triggering process restarts upon certificate expiry instead of streaming dynamic Envoy SDS updates. 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 DriftMounting static SVID certificates from disk or triggering process restarts upon certificate expiry instead of streaming dynamic Envoy SDS updates.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 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 configure Envoy TLS contexts to source X.509 SVIDs and Validation Contexts via Secret Discovery Service (SDS) connected over Unix Domain Sockets (UDS) to the SPIRE Workload API.

Engineers MUST ALWAYS configure Envoy TLS contexts to source X.509 SVIDs and Validation Contexts via Secret Discovery Service (SDS) connected over Unix Domain Sockets (UDS) to the SPIRE Workload API.

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 configure static certificate chains or private keys via file paths ('filename

Engineers MUST NOT configure static certificate chains or private keys via file paths ('filename: ...') in transport socket configurations when targeting SPIFFE-managed workloads.

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

SDS config sources MUST explicitly define 'api_type

SDS config sources MUST explicitly define 'api_type: GRPC' with 'transport_api_version: V3' referencing an in-process or local UDS Envoy gRPC cluster connected to SPIRE agent.

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

Common TLS contexts MUST enforce strict SPIFFE ID SAN validation using 'match_typed_subject_alt_names' with 'exact' or 'prefix' patterns against the SPIFFE trust domain.

Common TLS contexts MUST enforce strict SPIFFE ID SAN validation using 'match_typed_subject_alt_names' with 'exact' or 'prefix' patterns against the SPIFFE trust domain.

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

Services MUST mount the SPIRE Workload API Unix Domain Socket via a dedicated, secure shared volume (such as 'emptyDir

Services MUST mount the SPIRE Workload API Unix Domain Socket via a dedicated, secure shared volume (such as 'emptyDir: { medium: Memory }' or CSI driver) with restricted POSIX permissions.

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

Components NEVER trigger container or pod restarts to rotate expiring certificates

Components NEVER trigger container or pod restarts to rotate expiring certificates; all certificate transitions MUST complete in-memory via SDS streaming without draining non-expired connections.

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 SPIFFE/SPIRE Workload Identity Envoy SDS Automated Rotation Boundary critical for AI coding assistants?

Enforces dynamic, zero-downtime X.509 SVID renewal through Envoy Secret Discovery Service (SDS) integrated with the SPIRE Workload API over Unix Domain Sockets. Prevents connection drops, cold restarts, and validation failures under ultra-short TTL (<= 5-minute) rotation boundaries in zero-trust mesh architectures. 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 (Mounting static SVID certificates from disk or triggering process restarts upon certificate expiry instead of streaming dynamic Envoy SDS updates.) 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

SPIFFE/SPIRE