skills.rest
marcosgomesebury
marcosgomeseburyCOMMUNITY
Explore all skills by this author →
GitHub

kubernetes_debug

Diagnose Kubernetes pod failures in GKE clusters using status, events, and logs.

Updated Mar 17, 2026
Search Tags:#logs#remediation#kubernetes#events#gke#pod-diagnosis
One-click install
npx skills add https://github.com/marcosgomesebury/ebb-platform-ia --skill kubernetes-debug-marcosgomesebury
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubernetes_debug
Source: https://github.com/marcosgomesebury/ebb-platform-ia/tree/main/skills/kubernetes_debug
Command: npx skills add https://github.com/marcosgomesebury/ebb-platform-ia --skill kubernetes-debug-marcosgomesebury

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses Kubernetes pod issues in GKE clusters by collecting pod status, events, and logs to deliver actionable root-cause analyses and remediation steps.

Core Features & Use Cases

  • Automated diagnosis of common pod problems such as ImagePullBackOff, CrashLoopBackOff, Pending pods, and Workload Identity failures.
  • Aggregates pod status, recent events, and logs to provide step-by-step remediation guidance.
  • Supports cross-project scenarios (ebb-money-flows-dev, ebb-client-journey-dev, ebb-platform-dev) for consistent troubleshooting workflows.

Quick Start

Run the Kubernetes Debug Tool with the target pod name and namespace to generate a diagnostic report.

Frequently Asked Questions about kubernetes_debug

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

FAQPage Schema
How do I diagnose Kubernetes pod failures like ImagePullBackOff and CrashLoopBackOff?▼

Diagnose CrashLoopBackOff and ImagePullBackOff failures by collecting pod status, recent events, and container logs to identify root causes and output actionable remediation commands for your GKE cluster.

Why does my Kubernetes pod stay in a Pending state in GKE?▼

A Pending pod in GKE often results from resource constraints or scheduling failures; collecting pod status and cluster events helps identify root causes and outputs remediation steps to resolve the block.

Do I need kubectl and gcloud to troubleshoot GKE workload identity failures?▼

Yes, troubleshooting GKE Workload Identity failures requires kubectl and gcloud to collect pod status, events, and logs needed to diagnose the configuration issue and output recommended remediation commands.

Can I diagnose NetworkPolicy blocks and resource constraints across multiple GKE projects?▼

Yes, you can diagnose NetworkPolicy blocks and resource constraints across multiple ebb-dev projects by aggregating pod status and events to deliver consistent root-cause analysis and step-by-step remediation workflows.

What is the best way to fix Kubernetes pods that fail to pull images or crash on startup?▼

The best way to fix Kubernetes startup crashes and image pull failures is to aggregate pod status, events, and logs to pinpoint the exact failure point and generate targeted step-by-step remediation commands.

Related Skills

Explore More Software Engineering Skills→
fajshahfajshah
1

gke-multi-cloud-k8s

Provision and manage multi-cloud GKE clusters with kubectl connectivity.

Community
Advanced
ViktorBarzinViktorBarzin
5

k8s-nfs-mount-troubleshooting

Diagnose Kubernetes NFS mount failures causing ContainerCreating pod states.

Community
Advanced
cnoe-iocnoe-io
392

cluster-resource-health

Query EKS clusters via kubectl and report pod, node, and resource health.

Official
Intermediate
akin-ozerakin-ozer
290

k8s-debug

Diagnose Kubernetes pod failures, network issues, and cluster health with kubectl and Python 3.

Community
Intermediate