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: ebpf-sidecarless-mesh-l7-mtls-standard

eBPF Sidecarless Mesh L7 Microsegmentation and Kernel-Attested mTLS Enforcement Standard

Enforces strict kernel-space microsegmentation and transparent wire encryption via eBPF without injecting userspace Envoy sidecar proxies. By compiling L7 protocol inspection into sock_ops/sk_msg programs and offloading cryptographic transport to node-level WireGuard/IPsec kernels, this standard guarantees zero-copy socket redirection, sub-millisecond p99 latencies, and immune-to-tamper identity attestation.

Prohibited Anti-Pattern: Injecting Userspace Envoy Sidecars and Default-Permissive L4 NetworkPolicies with Terminated Userland TLS

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: eBPF Sidecarless Mesh L7 Microsegmentation and Kernel-Attested mTLS Enforcement Standard - Enforces strict kernel-space microsegmentation and transparent wire encryption via eBPF without injecting userspace Envoy sidecar proxies. By compiling L7 protocol inspection into sock_ops/sk_msg programs and offloading cryptographic transport to node-level WireGuard/IPsec kernels, this standard guarantees zero-copy socket redirection, sub-millisecond p99 latencies, and immune-to-tamper identity attestation.
globs: deployments/**/*.{yaml,yml}, k8s/**/*.{yaml,yml}, infra/**/*.{yaml,yml}, helm/**/*.{yaml,yml}, mesh/**/*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/ebpf-sidecarless-mesh-l7-mtls-standard"
---

# eBPF Sidecarless Mesh L7 Microsegmentation and Kernel-Attested mTLS Enforcement Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Injecting Userspace Envoy Sidecars and Default-Permissive L4 NetworkPolicies with Terminated Userland TLS

## System Constraints
You are a Principal Infrastructure & Security Architect enforcing zero-overhead, eBPF-driven sidecarless service mesh architectures. You must mandate kernel-level L7 microsegmentation, transparent kernel-space mTLS/WireGuard encryption, and SPIFFE-based identity attestation while strictly banning redundant userspace sidecar containers, unsegmented L4 wildcard policies, and userland proxy memory bloat.

## Strict Guidelines
- Engineers MUST ALWAYS enforce L7 microsegmentation via CiliumNetworkPolicy using sock_ops programs, strictly specifying HTTP method, path, and header invariants rather than loose L4 CIDRs.
- Engineers MUST ALWAYS enable kernel-space transparent wire encryption (Cilium WireGuard or IPsec engine) at the CNI layer to guarantee continuous transport encryption without container-level certificate injection.
- Engineers MUST NOT inject Envoy/Istio sidecar containers into workloads, preventing pod lifecycle race conditions and dual-stack userspace-kernel context-switching penalties.
- Services MUST attest cryptographic identity via SPIFFE/SPIRE integrated with eBPF identity maps (ipcache), validating identity at the socket layer before packet egress.
- Components NEVER permit cross-namespace egress without an explicit CiliumClusterwideNetworkPolicy mapping ingress identity selectors and explicit L7 rulesets.

## Bad vs Good Implementations
### Sidecarless eBPF L7 Microsegmentation with Kernel mTLS vs. Insecure Legacy L4 Policy

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Relies on a generic K8s L4 NetworkPolicy allowing any arbitrary HTTP path/verb across port 8080. Injects an Envoy sidecar container, creating duplicate network hops, high memory consumption, pod startup race conditions, and userspace TLS termination overhead.
```yaml
# ANTI-PATTERN: Permissive Kubernetes L4 NetworkPolicy relying on fragile userspace sidecar injection
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: payment-service-policy
  namespace: payments
spec:
  podSelector:
    matchLabels:
      app: payment-gateway
  ingress:
    - from:
        - podSelector:
            matchLabels:
              app: checkout-frontend
      ports:
        - protocol: TCP
          port: 8080
  policyTypes:
    - Ingress
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: payment-gateway
  namespace: payments
spec:
  template:
    metadata:
      annotations:
        # Unnecessary userspace sidecar consuming 128MB+ RAM and 2 extra TCP hops
        sidecar.istio.io/inject: "true"
    spec:
      containers:
        - name: gateway
          image: internal.registry/payments/gateway:v1.2.0
```

#### Production Standard (Correct)
> **Standard**: Implements deterministic eBPF microsegmentation: eliminates the sidecar container, uses kernel sockmap redirection to parse HTTP requests directly at L7, enforces exact verbs/paths, and mandates kernel-attested mutual authentication without userspace overhead.
```yaml
# PRODUCTION STANDARD: eBPF-native CiliumNetworkPolicy enforcing strict L7 methods with kernel-level identity verification
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: payment-service-l7-secure
  namespace: payments
spec:
  endpointSelector:
    matchLabels:
      app: payment-gateway
  ingress:
    - fromEndpoints:
        - matchLabels:
            app: checkout-frontend
            k8s:io.kubernetes.pod.namespace: checkout
      toPorts:
        - ports:
            - port: "8080"
              protocol: TCP
          rules:
            http:
              - method: "POST"
                path: "/api/v1/charge"
                headers:
                  - "X-Authenticated-Caller: checkout-service"
  # Kernel-enforced transparent encryption and identity attestation verification
  authentication:
    mode: required
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: payment-gateway
  namespace: payments
spec:
  template:
    metadata:
      annotations:
        # Sidecarless: BPF sockmap redirects traffic straight from app socket to kernel
        cilium.io/no-sidecar-required: "true"
    spec:
      containers:
        - name: gateway
          image: internal.registry/payments/gateway:v1.2.0
          resources:
            limits:
              memory: 256Mi
              cpu: 500m
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Inspector
Inspects and validates live CiliumNetworkPolicies, endpoint identities, and eBPF maps in cluster environments.
Recommended Agent Skills (askills.dev)

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

Cilium eBPF Diagnostics CLI
Runs kernel-level eBPF packet tracing, sockops map inspection, and microsegmentation policy validation.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: eBPF Sidecarless Mesh L7 Microsegmentation and Kernel-Attested mTLS Enforcement Standard

eBPF Sidecarless Mesh L7 Microsegmentation and Kernel-Attested mTLS Enforcement Standard defines an industrial-grade behavioral standard for devops engineering. Enforces strict kernel-space microsegmentation and transparent wire encryption via eBPF without injecting userspace Envoy sidecar proxies. By compiling L7 protocol inspection into sock_ops/sk_msg programs and offloading cryptographic transport to node-level WireGuard/IPsec kernels, this standard guarantees zero-copy socket redirection, sub-millisecond p99 latencies, and immune-to-tamper identity attestation. 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: Injecting Userspace Envoy Sidecars and Default-Permissive L4 NetworkPolicies with Terminated Userland TLS 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 DriftInjecting Userspace Envoy Sidecars and Default-Permissive L4 NetworkPolicies with Terminated Userland TLSCritical
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 enforce L7 microsegmentation via CiliumNetworkPolicy using sock_ops programs, strictly specifying HTTP method, path, and header invariants rather than loose L4 CIDRs.

Engineers MUST ALWAYS enforce L7 microsegmentation via CiliumNetworkPolicy using sock_ops programs, strictly specifying HTTP method, path, and header invariants rather than loose L4 CIDRs.

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 ALWAYS enable kernel-space transparent wire encryption (Cilium WireGuard or IPsec engine) at the CNI layer to guarantee continuous transport encryption without container-level certificate injection.

Engineers MUST ALWAYS enable kernel-space transparent wire encryption (Cilium WireGuard or IPsec engine) at the CNI layer to guarantee continuous transport encryption without container-level certificate injection.

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

Engineers MUST NOT inject Envoy/Istio sidecar containers into workloads, preventing pod lifecycle race conditions and dual-stack userspace-kernel context-switching penalties.

Engineers MUST NOT inject Envoy/Istio sidecar containers into workloads, preventing pod lifecycle race conditions and dual-stack userspace-kernel context-switching penalties.

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 attest cryptographic identity via SPIFFE/SPIRE integrated with eBPF identity maps (ipcache), validating identity at the socket layer before packet egress.

Services MUST attest cryptographic identity via SPIFFE/SPIRE integrated with eBPF identity maps (ipcache), validating identity at the socket layer before packet egress.

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 permit cross-namespace egress without an explicit CiliumClusterwideNetworkPolicy mapping ingress identity selectors and explicit L7 rulesets.

Components NEVER permit cross-namespace egress without an explicit CiliumClusterwideNetworkPolicy mapping ingress identity selectors and explicit L7 rulesets.

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 eBPF Sidecarless Mesh L7 Microsegmentation and Kernel-Attested mTLS Enforcement Standard critical for AI coding assistants?

Enforces strict kernel-space microsegmentation and transparent wire encryption via eBPF without injecting userspace Envoy sidecar proxies. By compiling L7 protocol inspection into sock_ops/sk_msg programs and offloading cryptographic transport to node-level WireGuard/IPsec kernels, this standard guarantees zero-copy socket redirection, sub-millisecond p99 latencies, and immune-to-tamper identity attestation. 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 (Injecting Userspace Envoy Sidecars and Default-Permissive L4 NetworkPolicies with Terminated Userland TLS) 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

eBPF