troubleshoot-kubernetes-api-server

What problem does it solve?

It helps you diagnose Kubernetes API Server incidents by mapping symptoms like webhook stalls, list storms, etcd latency cascades, memory cliffs, and RBAC/auth slowdowns to the specific Netdata-observed health signals and an operator-style diagnostic tree.

Core Features & Use Cases

• MCP-driven triage: Queries Netdata via MCP for Kubernetes API Server health contexts (for example request rate, dropped requests, audit events, workqueue adds/retries, and latency percentiles) to quickly isolate the failure archetype.
• Operator playbook alignment: Applies the Netdata operator playbook’s remediation logic by following the same dominant failure patterns, while using Netdata signals as the source of truth.
• Actionable verification loop: Re-runs targeted MCP verification queries after remediation to confirm signals return to expected bands and avoids “looks fixed” misdiagnoses.

Quick Start

Use the troubleshoot-kubernetes-api-server skill to pull the last 15–30 minutes of Kubernetes API Server MCP metrics for the affected node, identify the dominant failure archetype, and select the matching remediation path from the operator playbook.