EKS Troubleshooting

Automates Kubernetes/EKS issue investigations across deployment, networking, node, and ingress troubleshooting.

Updated Mar 1, 2026

Search Tags:#automation #investigation #troubleshooting #kubernetes #eks #kubectl #cluster

Ready to run

npx skills add https://github.com/kjenney/claude-devops --skill eks-troubleshooting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: EKS Troubleshooting
Source: https://github.com/kjenney/claude-devops/tree/main/skills/eks-troubleshooting
Command: npx skills add https://github.com/kjenney/claude-devops --skill eks-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Kubernetes/EKS environments often suffer from silent issues or misconfigurations that block deployments or disrupt service connectivity. This skill automates the investigation process by orchestrating the run-investigation.sh workflow and the eks-investigator agent to diagnose issues across a cluster.

Core Features & Use Cases

Automated EKS issue investigations using a guided CLI command and an agent-driven orchestrator.
Supports common issue types such as deployment, networking, node, and ingress to cover typical Kubernetes problems.
Provides example scripts and references to help operators reproduce and resolve failures quickly.

Quick Start

Trigger the investigation with the /eks-investigate command and follow on-screen prompts to collect the required context and resource details.

Frequently Asked Questions about EKS Troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I troubleshoot Kubernetes EKS deployment failures across a cluster?▼

To troubleshoot Kubernetes EKS deployment failures, this Skill automates issue investigations using a guided CLI command and an agent-driven orchestrator to diagnose problems across your cluster. It supports deployment, networking, node, and ingress troubleshooting.

What is the best way to investigate silent EKS misconfigurations that disrupt service connectivity?▼

The best way to investigate silent EKS misconfigurations is using automated orchestration that validates context and runs an eks-investigator agent. This workflow diagnoses connectivity disruptions and identifies misconfigurations blocking deployments.

How do I start an automated EKS investigation using kubectl?▼

You start an automated EKS investigation by triggering the /eks-investigate command and following on-screen prompts to collect required context and resource details. The workflow then orchestrates CLI and agent processes to diagnose the cluster.

Can I use this to troubleshoot Kubernetes networking and ingress issues?▼

Yes, you can use this to troubleshoot Kubernetes networking and ingress issues. The investigation scope explicitly covers deployment, networking, node, and ingress troubleshooting across Kubernetes clusters using guided example scripts.

How does automated EKS troubleshooting compare to manual kubectl cluster investigations?▼

Automated EKS troubleshooting orchestrates CLI and agent workflows with context validation, replacing manual kubectl cluster investigations. It provides a library of example scripts and references to help operators reproduce and resolve failures quickly.