Diagnose Kubernetes node health by inspecting conditions and resource usage.
npx skills add https://github.com/scitix/siclaw --skill node-health-check
Please help me install this Agent Skill. Skill: node-health-check Source: https://github.com/scitix/siclaw/tree/main/skills/core/node-health-check Command: npx skills add https://github.com/scitix/siclaw --skill node-health-check
This Skill helps diagnose and understand node-level issues in a Kubernetes cluster, such as nodes being NotReady or experiencing resource pressure.
MemoryPressure, DiskPressure, PIDPressure, and NetworkUnavailable.NotReady, this Skill can be used to investigate why, checking Kubelet status, network connectivity, and resource constraints.Use the node-health-check skill to diagnose issues with the node named 'worker-node-1'.
High-intent search queries and answers about installing and using this skill.
To diagnose a NotReady Kubernetes node, you need to inspect node conditions, resource allocation, and real-time usage. This process checks for Kubelet issues, network connectivity problems, and resource constraints to pinpoint the root cause of the node failure.
MemoryPressure and DiskPressure conditions in Kubernetes nodes are caused by resource exhaustion. Analyzing real-time CPU and memory usage against node capacity helps identify whether process overload or insufficient disk space is driving these specific node health issues.
You need kubectl to troubleshoot Kubernetes node health issues, while the Metrics Server is optional. Metrics Server provides real-time resource usage data, which enhances the analysis of CPU and memory allocation against the actual node capacity during diagnostics.
To check Kubernetes node resource allocation and real-time usage, inspect node conditions and analyze CPU and memory metrics. This identifies resource pressure issues like PIDPressure and NetworkUnavailable by comparing current consumption against total node capacity.
The best way to perform root cause analysis for Kubernetes node failures is to inspect node conditions and resource allocation systematically. This approach guides you through checking Kubelet status, network connectivity, and resource constraints to isolate the exact failure trigger.
dapperdiversDiagnose Kubernetes metrics-server failures and generate structured health reports.
razorpayRun kubectl queries via Friday MCP to diagnose Kubernetes pod failures.
sarimofficialAnalyze Kubernetes cluster health from kagent outputs and generate prioritized remediation recommendations.
haozhx23Automate installation and management of cluster add-ons like Karpenter.