Diagnose Kubernetes pod failures and analyze container logs via kubectl or oc.
npx skills add https://github.com/kagenti/kagenti --skill k8s-kagenti
Please help me install this Agent Skill. Skill: k8s Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/k8s Command: npx skills add https://github.com/kagenti/kagenti --skill k8s-kagenti
This Skill helps users diagnose and resolve issues within Kubernetes clusters, reducing downtime and improving application stability.
Use the k8s skill to check the status of all pods in the 'default' namespace.
High-intent search queries and answers about installing and using this skill.
To troubleshoot Kubernetes pods in CrashLoopBackOff or ImagePullBackOff, you need to check pod statuses, review recent cluster events, and examine container logs to identify the root cause of the failures.
The best way to analyze Kubernetes pod logs for errors is to query and review container outputs directly, which helps pinpoint application-level issues and resolve downtime within your running clusters.
Yes, you need kubectl or oc CLI access to interact with the Kubernetes API, which is required for diagnosing pod failures, checking platform health, and performing iterative debugging on running clusters.
You can check the health of Kubernetes deployments and services by verifying the status of core components and reviewing recent events to ensure platform health and improve application stability.
Yes, you can debug pending pods in a Kubernetes cluster by diagnosing common pod failures, which includes checking pod statuses and analyzing recent events to identify why pods remain in a Pending state.
eveldQuery Kubernetes resources to determine cluster state and resource health.
cyhinverseGuide production deployments through a five-phase workflow with rollback readiness.
BagelHoleConfigure New Relic agents, NRQL queries, dashboards, and alerts.
huynguyenhRun kubectl commands to debug and monitor Kubernetes EKS clusters.
