Skip to content

GKE Storage Troubleshooting

Diagnoses and fixes persistent-storage failures on Google Kubernetes Engine (GKE) clusters.

Repository
google/skills
Stars
21,782
Licence
Apache-2.0
Files
2 files

What it does

When installed, the agent follows a structured playbook for GKE storage problems: pods stuck in ContainerCreating, volumes that fail to attach or mount, disk performance and node storage pressure, volume expansion not showing inside containers, Local SSD or Hyperdisk creation errors, and Cloud Storage FUSE out-of-memory events. It first gathers cluster details, then runs read-only kubectl and gcloud diagnostics, classifies the symptom, and applies only the matching fix branch. If the cluster is unreachable, it gives the exact commands for a human to run and proposes a configuration correction instead.

Great for

  • Platform or DevOps engineers debugging stuck GKE pods with volume errors
  • Teams running stateful workloads on GKE who hit Regional PD or Hyperdisk scheduling problems
  • Operators who want a guided runbook for storage incidents rather than searching docs

Skip it if

  • Routine storage provisioning or writing StorageClass and PVC manifests; the file says to use the separate gke-storage skill for that
  • Non-GKE Kubernetes or non-Google clouds, since the guidance is specific to GKE and gcloud
  • Unattended production changes: the skill proposes corrections to be applied via GitOps, and a wrong fix could affect live data

Try asking

  • “My pod is stuck in ContainerCreating with a FailedAttachVolume event on a regional PD. Help me diagnose it.”
  • “Our N4 node pool is causing Pods with PD volumes to stay Pending. What should we change?”
  • “Nodes in my GKE cluster are reporting StoragePressureDetected. Walk me through the diagnosis.”
  • “Cloud Storage FUSE sidecar keeps getting OOM killed. What are the likely causes?”
Step-by-step guide: how to use GKE Storage TroubleshootingInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the Apache-2.0 licence and an attribution note.

    gke-storage-troubleshooting.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip gke-storage-troubleshooting.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip gke-storage-troubleshooting.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent the pod name, namespace, cluster name, location and project up front so it does not need to guess.
  • Paste the output of kubectl describe pod and kubectl get events; the classification step depends on those signals.
  • Review any proposed manifest change before applying it, especially StorageClass changes that affect existing volumes.

What's inside

  • references/attribution.md
  • SKILL.md

Redistributed unmodified from google/skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.