What problem does it solve?
Configuring persistent storage for GKE clusters is complex, with multiple storage options, access modes, and configuration requirements that can lead to misconfigured resources, performance issues, or data loss for stateful workloads.
Core Features & Use Cases
- StorageClass Configuration: Set up default and custom StorageClasses for persistent disks, Filestore, and GCS FUSE aligned with GKE golden path defaults.
- PersistentVolumeClaim Provisioning: Create PVCs for block storage (ReadWriteOnce for databases) and shared file storage (ReadWriteMany via Filestore for multi-pod workloads).
- GCS FUSE Integration: Mount GCS buckets directly as volumes for data pipelines, ML training data, and log storage without managing PVCs.
Use Case: A DevOps engineer can use this skill to provision a high-availability regional persistent disk for a stateful PostgreSQL database on GKE, or set up a shared Filestore volume for a multi-pod content management system.
Quick Start
Use the gke-storage skill to create a ReadWriteOnce persistent volume claim for a stateful database workload on your GKE cluster.