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: gitops-ebpf-canary-metric-gates

Kernel-Level eBPF Metric-Gated GitOps Canary Rollbacks

Enforces sub-second progressive canary delivery rollbacks by decoupling promotion decisions from aggregated application log collectors and relying on real-time kernel-level eBPF socket tracing. Monitors raw TCP RTT latency deltas and kernel HTTP error transitions via ring-buffers directly in the host transport layer, triggering zero-trust rollbacks before corrupted payloads propagate across user-space mesh networks.

Prohibited Anti-Pattern: User-Space Log-Scraped Progressive Delivery with Delayed Rollback Horizons

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kernel-Level eBPF Metric-Gated GitOps Canary Rollbacks - Enforces sub-second progressive canary delivery rollbacks by decoupling promotion decisions from aggregated application log collectors and relying on real-time kernel-level eBPF socket tracing. Monitors raw TCP RTT latency deltas and kernel HTTP error transitions via ring-buffers directly in the host transport layer, triggering zero-trust rollbacks before corrupted payloads propagate across user-space mesh networks.
globs: deploy/**/*.{yaml,yml}, k8s/**/*.{yaml,yml}, monitoring/**/*.{yaml,yml}, src/observability/**/*.{ts,go,c,rs}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/gitops-ebpf-canary-metric-gates"
---

# Kernel-Level eBPF Metric-Gated GitOps Canary Rollbacks

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: User-Space Log-Scraped Progressive Delivery with Delayed Rollback Horizons

## System Constraints
You are a Principal Platform Engineer and Site Reliability Architect enforcing zero-trust progressive delivery with eBPF-driven automated rollbacks. Mandate kernel-level socket latency and TCP state tracking as authoritative metric gates. Eliminate all reliance on user-space telemetry or asynchronous logging pipelines for canary health decisions.

## Strict Guidelines
- Engineers MUST ALWAYS configure canary metric verification queries against eBPF-derived metrics (e.g., direct sock:inet_sock_set_state or tcp_set_state maps) rather than aggregated Prometheus metrics derived from parsed stdout logs.
- Engineers MUST NOT rely on log aggregators (e.g., FluentBit, Loki, Vector) for canary circuit-breaker thresholds, as log buffering introduces 5 to 30-second rollback blind spots.
- Canary analysis gates MUST evaluate TCP RTT (Smooth Round-Trip Time) degradation and TCP retransmit spikes at the cgroup/socket boundary directly in the analysis interval.
- Progressive delivery controllers (Argo Rollouts, Flagger) MUST trigger step failure if socket-level HTTP 5xx transitions exceed 0.5% within a sliding 5-second kernel histogram window.
- Services MUST emit deterministic trace IDs across kernel eBPF tracepoints (`sys_enter_writev` / `tcp_sendmsg`) to attribute latency spikes specifically to the canary pod IP.

## Bad vs Good Implementations
### Progressive Delivery Metric Template Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Evaluating application stdout logs via Prometheus introduces multi-second ingestion lag, 5-minute sampling windows, and fails to capture socket-layer connection resets (RSTs) and TCP queue drops.
```yaml
# Anti-Pattern: Metric gate depends on asynchronous, parsed user-space stdout logs
apiVersion: argoproj.io/v1alpha1
kind: AnalysisTemplate
metadata:
  name: canary-success-rate
spec:
  metrics:
  - name: success-rate
    interval: 60s
    successCondition: result[0] >= 0.99
    failureLimit: 3
    provider:
      prometheus:
        address: http://prometheus.monitoring.svc.cluster.local:9090
        query: |
          sum(rate(app_log_http_requests_total{status=~"2..",pod=~"web-canary.*"}[5m]))
          /
          sum(rate(app_log_http_requests_total{pod=~"web-canary.*"}[5m]))
```

#### Production Standard (Correct)
> **Standard**: Binds directly to eBPF kernel probes monitoring real-time TCP RTT in microseconds and raw kernel-parsed HTTP frames, catching regressions within 2 to 4 seconds and instantly triggering an automated GitOps rollback.
```yaml
# Production Invariant: Sub-second kernel-level eBPF socket metric gate
apiVersion: argoproj.io/v1alpha1
kind: AnalysisTemplate
metadata:
  name: canary-ebpf-socket-gate
spec:
  metrics:
  - name: tcp-rtt-p99
    interval: 2s
    count: 3
    failureLimit: 1
    successCondition: result[0] <= 15.0
    provider:
      prometheus:
        address: http://prometheus-ebpf.monitoring.svc.cluster.local:9090
        query: |
          histogram_quantile(0.99, sum(rate(ebpf_sock_tcp_rtt_microseconds_bucket{pod_role="canary"}[5s])) by (le)) / 1000
  - name: kernel-http-5xx-rate
    interval: 2s
    count: 2
    failureLimit: 0
    successCondition: result[0] < 0.005
    provider:
      prometheus:
        address: http://prometheus-ebpf.monitoring.svc.cluster.local:9090
        query: |
          sum(rate(ebpf_http_kernel_responses_total{pod_role="canary",status_class="5xx"}[5s]))
          /
          sum(rate(ebpf_http_kernel_responses_total{pod_role="canary"}[5s]))
```
Recommended MCP Servers (mcp-serverlist.com)

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

Prometheus Real-Time Metric Inspector
MCP endpoint for running sub-second PromQL verification queries against eBPF metric exports.
Kubernetes Resource Inspector
MCP interface for validating AnalysisTemplate and Canary CRD schemas and current rollout phases.
Recommended Agent Skills (askills.dev)

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

bpftool Socket Map Analyzer
Validates eBPF socket map telemetry, BPF ring-buffers, and kernel tracepoint attachments on the canary host nodes.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kernel-Level eBPF Metric-Gated GitOps Canary Rollbacks

Kernel-Level eBPF Metric-Gated GitOps Canary Rollbacks defines an industrial-grade behavioral standard for devops engineering. Enforces sub-second progressive canary delivery rollbacks by decoupling promotion decisions from aggregated application log collectors and relying on real-time kernel-level eBPF socket tracing. Monitors raw TCP RTT latency deltas and kernel HTTP error transitions via ring-buffers directly in the host transport layer, triggering zero-trust rollbacks before corrupted payloads propagate across user-space mesh networks. 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: User-Space Log-Scraped Progressive Delivery with Delayed Rollback Horizons 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 DriftUser-Space Log-Scraped Progressive Delivery with Delayed Rollback HorizonsCritical
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 canary metric verification queries against eBPF-derived metrics (e.g., direct sock

Engineers MUST ALWAYS configure canary metric verification queries against eBPF-derived metrics (e.g., direct sock:inet_sock_set_state or tcp_set_state maps) rather than aggregated Prometheus metrics derived from parsed stdout logs.

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 log aggregators (e.g., FluentBit, Loki, Vector) for canary circuit-breaker thresholds, as log buffering introduces 5 to 30-second rollback blind spots.

Engineers MUST NOT rely on log aggregators (e.g., FluentBit, Loki, Vector) for canary circuit-breaker thresholds, as log buffering introduces 5 to 30-second rollback blind spots.

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

Canary analysis gates MUST evaluate TCP RTT (Smooth Round-Trip Time) degradation and TCP retransmit spikes at the cgroup/socket boundary directly in the analysis interval.

Canary analysis gates MUST evaluate TCP RTT (Smooth Round-Trip Time) degradation and TCP retransmit spikes at the cgroup/socket boundary directly in the analysis interval.

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

Progressive delivery controllers (Argo Rollouts, Flagger) MUST trigger step failure if socket-level HTTP 5xx transitions exceed 0.5% within a sliding 5-second kernel histogram window.

Progressive delivery controllers (Argo Rollouts, Flagger) MUST trigger step failure if socket-level HTTP 5xx transitions exceed 0.5% within a sliding 5-second kernel histogram window.

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 emit deterministic trace IDs across kernel eBPF tracepoints (`sys_enter_writev` / `tcp_sendmsg`) to attribute latency spikes specifically to the canary pod IP.

Services MUST emit deterministic trace IDs across kernel eBPF tracepoints (`sys_enter_writev` / `tcp_sendmsg`) to attribute latency spikes specifically to the canary pod IP.

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 Kernel-Level eBPF Metric-Gated GitOps Canary Rollbacks critical for AI coding assistants?

Enforces sub-second progressive canary delivery rollbacks by decoupling promotion decisions from aggregated application log collectors and relying on real-time kernel-level eBPF socket tracing. Monitors raw TCP RTT latency deltas and kernel HTTP error transitions via ring-buffers directly in the host transport layer, triggering zero-trust rollbacks before corrupted payloads propagate across user-space mesh networks. 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 (User-Space Log-Scraped Progressive Delivery with Delayed Rollback Horizons) 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

Kernel-Level