📋 Copy Blueprint Command { } Inspect JSON API Ground-Truth Source ↗

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor

### 1. The Workflow Bottleneck & Problem Statement On-call engineers woken up at 3:00 AM waste precious minutes running repetitive `kubectl describe` and `kubectl logs` commands across clusters. ### 2. Synthesized Agent Architecture & Connected Stack **Kubernetes Pod CrashLoopBackOff & OOMKilled Root-Cause Triage** (`kubernetes-crashloop-auto-diagnostician`) is a verified production blueprint curated from **@steipete**'s real-world implementation. - **Primary Capability:** Detects restarting Kubernetes pods, pulls previous container logs (`--previous`), correlates memory limit spikes in Datadog, and proposes the manifest patch. - **Connected Tool Stack:** Kubernetes MCP, Datadog MCP, PagerDuty MCP, GitHub MCP - **Execution Governance:** `Read-Only Discovery` → `Deterministic Policy Check` → `Ask-First Human Approval` - **Certified Builder Source:** [@steipete](https://github.com/Flux159/mcp-server-kubernetes) ### 3. Step-by-Step Implementation Blueprint 1. **Trigger & Data Ingestion:** Configure your agent routine to watch **Kubernetes MCP** on a scheduled cadence or event webhook. Treat all external text as untrusted data inside XML fences. 2. **Cross-System Enrichment & Verification:** Query **Datadog MCP** to validate live capacity, account status, or code state before generating recommendations. 3. **Human-in-the-Loop Action Staging:** Post a structured summary card to **GitHub MCP** with 1-click approve/edit controls so your team retains full oversight. ### 4. Copy-Paste System Prompt & Routine Configuration ```text Implement the 'Kubernetes Pod CrashLoopBackOff & OOMKilled Root-Cause Triage' workflow curated with @steipete. 1. OBJECTIVE: Detects restarting Kubernetes pods, pulls previous container logs (`--previous`), correlates memory limit spikes in Datadog, and proposes the manifest patch. 2. CONNECTED TOOL STACK: Kubernetes MCP, Datadog MCP, PagerDuty MCP, GitHub MCP 3. STEP-BY-STEP EXECUTION LOOP: - Step A (Ingest & Ground): Query live inputs from Kubernetes MCP and cross-reference state in Datadog MCP. - Step B (Analyze & Validate): Apply strict filtering rules, verify schema/policy constraints, and flag any anomalies or missing fields. - Step C (Stage & Report): Prepare the structured output, draft replies/tickets in GitHub MCP, and request human confirmation before executing any external send or production write. ``` ### 5. Measured ROI & Production Impact - **Verified Outcome:** Delivers a complete root-cause diagnosis and ready-to-apply resource/config diff within 60 seconds of a page. - **Builder Portfolio:** [Explore all capabilities by @steipete →](/u/steipete)

Tags: #kubernetes-crashloop-auto-diagnostician#use-case#security-ops#steipete#kubernetes-mcp#datadog-mcp

View All 16 Items by @steipete →

mcp · ⚡ 81

GitHub Official MCP — Repositories, Pull Requests, Actions & Code Search

Official GitHub MCP server for searching repositories, inspecting PR diffs and review comments, triaging issues, and reading GitHub Actions workflow runs.

template · ⚡ 91

Matter Smart Home & Fleet Robotics Coordinator

Coordinates Matter-compatible robotic vacuums, mowers, and home sensors around family schedules, quiet hours, and local weather forecasts.

use case · ⚡ 86

Autonomous Test-Driven Refactoring & CI Self-Healing Loop

Executes large-scale TypeScript/Swift codebase migrations in small atomic commits, running the test suite after each step and self-healing CI failures.