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: tetragon-ebpf-syscall-ringbuffer-invariants

Tetragon eBPF Synchronous Namespace Containment and Ring-Buffer Flow Invariants

Enforces deterministic, synchronous kernel-space enforcement using Tetragon TracingPolicies rather than asynchronous userspace audit consumers. Guarantees zero-loss telemetry under extreme I/O saturation by configuring dedicated BPF perf/ring buffer sizing, per-CPU memory reservation, and mandatory synchronous SIGKILL/kprobe action responses on container escape attempts.

Prohibited Anti-Pattern: Asynchronous Userspace Filtering and Unbounded BPF Event Buffers Causing Event Drops and Escape Window

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tetragon eBPF Synchronous Namespace Containment and Ring-Buffer Flow Invariants - Enforces deterministic, synchronous kernel-space enforcement using Tetragon TracingPolicies rather than asynchronous userspace audit consumers. Guarantees zero-loss telemetry under extreme I/O saturation by configuring dedicated BPF perf/ring buffer sizing, per-CPU memory reservation, and mandatory synchronous SIGKILL/kprobe action responses on container escape attempts.
globs: deploy/tetragon/**/*.yaml, k8s/**/*.yaml, policies/**/*.yaml, src/security/**/*.ts
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tetragon-ebpf-syscall-ringbuffer-invariants"
---

# Tetragon eBPF Synchronous Namespace Containment and Ring-Buffer Flow Invariants

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Asynchronous Userspace Filtering and Unbounded BPF Event Buffers Causing Event Drops and Escape Window

## System Constraints
You are a Principal Engineer enforcing eBPF Tetragon Real-Time Syscall Interception & Ring-Buffer Flow Invariants. Mandate synchronous kernel-level enforcement actions (Sigkill) inside kprobes/tracepoints, prevent asynchronous userspace enforcement gaps, and eliminate buffer drops through strictly bounded event filtering and adequately provisioned ring buffers.

## Strict Guidelines
- Engineers MUST ALWAYS configure synchronous in-kernel enforcement (`action: Sigkill`) in Tetragon TracingPolicy specs when intercepting unauthorized namespace transitions or capability abuses.
- Engineers MUST NOT rely on asynchronous userspace processing (such as Tetragon gRPC daemon clients or fluent-bit pipelines) to trigger reactive isolation or kill primitives.
- Code SHOULD enforce strict in-kernel filter selectors (`matchArgs`, `matchNamespaces`, `matchPIDs`) to drop uninteresting telemetry in kernel space before writing to the BPF ring buffer.
- Services MUST monitor `tetragon_ringbuf_perf_event_lost_total` and configure memory-backed ring buffers with explicit size allocations matching node core counts.
- Components NEVER permit permissive wildcard syscall hooks on high-frequency paths (e.g., `sys_enter_read`, `sys_enter_write`) without strict pid/binary match filters.

## Bad vs Good Implementations
### Tetragon TracingPolicy Enforcement vs Asynchronous Log Audit

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: This policy logs all setns syscalls across the host to the userspace ring buffer without in-kernel filtering. Under heavy I/O, the ring buffer overflows, dropping telemetry events and allowing an attacker to transition namespaces undetected and unblocked before userspace can react.
```yaml
# Anti-Pattern: Asynchronous observation without kernel-level enforcement
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: audit-namespace-escape
spec:
  kprobes:
    - call: "sys_setns"
      syscall: true
      args:
        - index: 0
          type: "int"
        - index: 1
          type: "int"
      # Missing in-kernel selectors and action; sends all events to userspace ring buffer

```

#### Production Standard (Correct)
> **Standard**: Evaluates namespaces and syscall flags entirely in kernel context via BPF helpers, synchronously terminating the violating task via Sigkill before the syscall completes, while eliminating ring buffer congestion.
```yaml
# Correct Invariant: Synchronous in-kernel enforcement with targeted filters
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: block-namespace-escape
spec:
  kprobes:
    - call: "sys_setns"
      syscall: true
      args:
        - index: 0
          type: "int"
        - index: 1
          type: "int"
      selectors:
        - matchNamespaces:
            - namespace: Pid
              operator: NotIn
              values: ["host"]
          matchArgs:
            - index: 1
              operator: Mask
              values: ["0x40000000"] # CLONE_NEWPID
          matchActions:
            - action: Sigkill

```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource MCP
Inspects and validates live cluster TracingPolicy CRDs and Tetragon daemon metrics.
Recommended Agent Skills (askills.dev)

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

Tetragon CLI Integration
Directly streams and validates Tetragon sensor states and export streams for dropped events.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tetragon eBPF Synchronous Namespace Containment and Ring-Buffer Flow Invariants

Tetragon eBPF Synchronous Namespace Containment and Ring-Buffer Flow Invariants defines an industrial-grade behavioral standard for devops engineering. Enforces deterministic, synchronous kernel-space enforcement using Tetragon TracingPolicies rather than asynchronous userspace audit consumers. Guarantees zero-loss telemetry under extreme I/O saturation by configuring dedicated BPF perf/ring buffer sizing, per-CPU memory reservation, and mandatory synchronous SIGKILL/kprobe action responses on container escape attempts. 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: Asynchronous Userspace Filtering and Unbounded BPF Event Buffers Causing Event Drops and Escape Window 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 DriftAsynchronous Userspace Filtering and Unbounded BPF Event Buffers Causing Event Drops and Escape WindowCritical
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 synchronous in-kernel enforcement (`action

Engineers MUST ALWAYS configure synchronous in-kernel enforcement (`action: Sigkill`) in Tetragon TracingPolicy specs when intercepting unauthorized namespace transitions or capability abuses.

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 asynchronous userspace processing (such as Tetragon gRPC daemon clients or fluent-bit pipelines) to trigger reactive isolation or kill primitives.

Engineers MUST NOT rely on asynchronous userspace processing (such as Tetragon gRPC daemon clients or fluent-bit pipelines) to trigger reactive isolation or kill primitives.

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 SHOULD enforce strict in-kernel filter selectors (`matchArgs`, `matchNamespaces`, `matchPIDs`) to drop uninteresting telemetry in kernel space before writing to the BPF ring buffer.

Code SHOULD enforce strict in-kernel filter selectors (`matchArgs`, `matchNamespaces`, `matchPIDs`) to drop uninteresting telemetry in kernel space before writing to the BPF ring buffer.

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 monitor `tetragon_ringbuf_perf_event_lost_total` and configure memory-backed ring buffers with explicit size allocations matching node core counts.

Services MUST monitor `tetragon_ringbuf_perf_event_lost_total` and configure memory-backed ring buffers with explicit size allocations matching node core counts.

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 permissive wildcard syscall hooks on high-frequency paths (e.g., `sys_enter_read`, `sys_enter_write`) without strict pid/binary match filters.

Components NEVER permit permissive wildcard syscall hooks on high-frequency paths (e.g., `sys_enter_read`, `sys_enter_write`) without strict pid/binary match filters.

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 Tetragon eBPF Synchronous Namespace Containment and Ring-Buffer Flow Invariants critical for AI coding assistants?

Enforces deterministic, synchronous kernel-space enforcement using Tetragon TracingPolicies rather than asynchronous userspace audit consumers. Guarantees zero-loss telemetry under extreme I/O saturation by configuring dedicated BPF perf/ring buffer sizing, per-CPU memory reservation, and mandatory synchronous SIGKILL/kprobe action responses on container escape attempts. 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 (Asynchronous Userspace Filtering and Unbounded BPF Event Buffers Causing Event Drops and Escape Window) 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

Tetragon