skills.rest
gke-labs
gke-labsOFFICIAL
Explore all skills by this author →
GitHub

gke-workload-troubleshooting

Diagnose GKE workload failures by analyzing pod states, namespace events, and application logs.

42|32|Updated May 7, 2026
Search Tags:#devops#troubleshooting#kubernetes#diagnostics#sre#gke
One-click install
npx skills add https://github.com/gke-labs/kube-agents --skill gke-workload-troubleshooting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gke-workload-troubleshooting
Source: https://github.com/gke-labs/kube-agents/tree/main/agents/cluster/skills/gke-workload-troubleshooting
Command: npx skills add https://github.com/gke-labs/kube-agents --skill gke-workload-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual toil of investigating GKE workload failures by providing a standardized, automated diagnostic workflow for crash loops, resource exhaustion, and connectivity issues.

Core Features & Use Cases

  • Systematic Diagnostics: Automatically analyzes pod status, event logs, and container exit codes to pinpoint root causes.
  • Evidence-Based RCA: Correlates infrastructure events with application logs to differentiate between code bugs and configuration drift.
  • Use Case: When a critical microservice enters a CrashLoopBackOff, use this skill to identify if the failure is due to an OOMKilled event or a missing secret, and generate the necessary manifest patch.

Quick Start

Use the gke-workload-troubleshooting skill to diagnose the payment-api workload in the checkout namespace within the production cluster.

Frequently Asked Questions about gke-workload-troubleshooting

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

FAQPage Schema
How do I automate GKE workload troubleshooting for CrashLoopBackOff?▼

Automate GKE workload troubleshooting by analyzing pod states, namespace events, and container exit codes to pinpoint root causes like OOMKilled events or missing secrets, then generate manifest patches.

What is the best way to find the root cause of Kubernetes pod failures in production?▼

Find the root cause of Kubernetes pod failures by correlating infrastructure events with application logs within a specific time window to differentiate between code bugs and configuration drift.

Can I use this to diagnose OOMKilled and network timeout errors in GKE?▼

Yes, you can diagnose OOMKilled and network timeout errors in GKE. The skill systematically analyzes resource exhaustion, crash loops, and mounting errors to identify failure root causes.

Do I need read-only access to cluster credentials for Kubernetes diagnostics?▼

Yes, you need read-only access to GKE cluster credentials and Cloud Logging to perform root cause analysis and generate configuration corrections for failing workloads.

How does this diagnostic process differentiate application code bugs from configuration drift?▼

It differentiates code bugs from configuration drift through evidence-based root cause analysis, correlating infrastructure events with application logs to isolate the exact failure trigger.

Related Skills

Explore More Software Engineering Skills→
ObolNetworkObolNetwork
10

obol-stack

Monitor Obol Stack Kubernetes pods, logs, services, and deployments via the Kubernetes API.

Official
Intermediate
jassicsjassics
6

k8s-workload-hardening

Review and apply Pod Security Standards to harden Kubernetes workloads.

Community
Advanced
rohitg00rohitg00
944

k8s-diagnostics

Diagnose Kubernetes cluster health, metrics, and resource differences across namespaces.

Community
Intermediate
razorpayrazorpay
31

k8s-debugger

Run kubectl queries via Friday MCP to diagnose Kubernetes pod failures.

Official
Advanced