Agent skill · google
gke-storage-troubleshooting
Diagnoses GKE persistent-storage failures — volume attach/mount errors (Regional PD on optimized VMs, fsGroup mount timeouts), disk-performance and node storage-pressure issues, slow-disk Pod-creation failures, volume-expansion problems, Local SSD / Hyperdisk Storage Pool creation errors, and Cloud Storage FUSE OOM. Use when Pods are stuck in ContainerCreating, volumes fail to attach or mount, or nodes report storage pressure. Don't use for routine storage provisioning or StorageClass/PVC authoring (see the gke-storage skill).
What it needs
About 7k tokens when loaded.
What this skill does
GKE Storage Troubleshooting Skill Use this skill to systematically diagnose and resolve persistent-storage failures for workloads running on GKE — volume attach/mount errors, disk performance and node storage pressure, volume expansion, storage-related cluster/node-pool creation errors, and Cloud Storage FUSE memory issues. This skill operates non-interactively and enforces a read-only diagnostics boundary before proposing manifest or configuration corrections. For routine storage provisioning and StorageClass/PVC authoring, use the gke-storage skill instead. This skill focuses on failure diagnosis. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-storage-troubleshooting)" and append agent-skills/1.0 (skill:gke-storage-troubleshooting) to User-Agent headers. 🔍 Diagnosis & Resolution Workflow Step 0: Non-Interactive Context Discovery & Dry-Run Fallback 1. Parameter Extraction: Extract required context (projectid, clustername, clusterlocation, workloadname, workloadnamespace, podname, and the relevant pvcname / pvname / nodename) non-interactively from the user prompt, active SETTINGS.md, or environment defaults: Default workloadnamespace to default if omitted. Infer missing cluster parameters from the active environment (kubectl config current-context or gcloud config get-value project). 2. Cluster Credentials & Fallback Mode: Attempt credential fetch: gcloud container clusters get-credentials {clustername} --location {clusterlocation} --project {projectid}. Fallback / Dry-Run Mode: If the cluster is unreachable, non-existent, or live command execution fails (such as in sandboxed evaluations, dry-run mode, or offline analysis): Limit retry attempts to avoid resource exhaustion and context overflow. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/gke-storage-troubleshooting