What problem does it solve? Choosing and configuring the right storage on Google Kubernetes Engine is error-prone: teams must pick between Persistent Disk, Filestore, GCS FUSE, and Parallelstore, write correct StorageClass and PVC manifests, and handle expansion and access modes correctly. This Skill provides validated manifests and decision guidance for GKE storage provisioning. ## Core Features & Use Cases - StorageClass and PVC manifests: Ready-to-use YAML for block storage (ReadWriteOnce), shared Filestore volumes (ReadWriteMany), and custom regional SSD classes with volume expansion enabled. - GCS FUSE bucket mounts: Mount Cloud Storage buckets directly as pod volumes using the gcsfuse CSI driver with Workload Identity, no PVC required. - Volume expansion guidance: Resize existing PVCs via kubectl patch or MCP tools when the StorageClass allows expansion. - Use Case: A database workload needs high-IOPS storage. Apply the premium-rwo PVC manifest, then later expand it from 100Gi to 200Gi with a single patch command. ## Quick Start Ask the assistant to create a GKE PersistentVolumeClaim for a database using the premium-rwo StorageClass with volume expansion enabled.