Catalog
google/gke-storage

google

gke-storage

Manages GKE storage, including PVCs, PersistentVolumes, Filestore, and GCS FUSE. Use when configuring GKE storage, creating PVCs, or setting up GCS FUSE on GKE. Don't use for database administration or replication strategies outside volume provisioning context.

New~1.2kUpdated Jun 28, 2026

GKE Storage

This reference covers storage configuration for GKE clusters including persistent disks, file storage, and cloud storage integration.

MCP Tools: apply_k8s_manifest, get_k8s_resource, describe_k8s_resource, get_cluster

Golden Path Storage Defaults

The golden path Autopilot config enables these CSI drivers:

Driver Golden Path Access Mode Use Case
Compute Engine Enabled (default) ReadWriteOnce Block storage for
: Persistent Disk : : : databases, :
: CSI : : : single-pod workloads :
Google Cloud Enabled ReadWriteMany Shared NFS for
: Filestore CSI : : : multi-pod access :
Cloud Storage Enabled ReadWriteMany / Mount GCS buckets as
: FUSE CSI : : ReadOnlyMany : volumes :
Parallelstore Enabled ReadWriteMany High-performance
: CSI : : : parallel file system :
Boot disk type pd-balanced N/A Node boot disks

StorageClasses

Default StorageClasses

GKE provides built-in StorageClasses:

StorageClass Disk Type Use Case
standard-rwo pd-standard Cost-effective, low IOPS
premium-rwo pd-ssd High IOPS, databases
standard-rwx Filestore (Basic HDD) Shared NFS
premium-rwx Filestore (Basic SSD) Shared NFS, higher performance

Custom StorageClass

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast-regional
provisioner: pd.csi.storage.gke.io
parameters:
  type: pd-ssd
  replication-type: regional-pd    # Replicate across 2 zones
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true         # Always enable for production

PersistentVolumeClaims

Block Storage (ReadWriteOnce)

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: database-pvc
spec:
  accessModes:
  - ReadWriteOnce
  storageClassName: premium-rwo
  resources:
    requests:
      storage: 100Gi

Shared File Storage (ReadWriteMany via Filestore)

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: shared-data
spec:
  accessModes:
  - ReadWriteMany
  storageClassName: standard-rwx
  resources:
    requests:
      storage: 1Ti    # Filestore minimum is 1 TiB for Basic tier

GCS Bucket Mount (Cloud Storage FUSE)

Mount a GCS bucket as a volume without a PVC:

apiVersion: v1
kind: Pod
metadata:
  name: gcs-reader
  annotations:
    gke-gcsfuse/volumes: "true"
spec:
  containers:
  - name: reader
    image: busybox
    command: ["ls", "/data"]
    volumeMounts:
    - name: gcs-bucket
      mountPath: /data
  volumes:
  - name: gcs-bucket
    csi:
      driver: gcsfuse.csi.storage.gke.io
      readOnly: true
      volumeAttributes:
        bucketName: <BUCKET_NAME>

Requires Workload Identity for the pod's service account to have storage.objectViewer on the bucket.

Volume Expansion

If allowVolumeExpansion: true is set on the StorageClass, resize by updating the PVC:

# kubectl
kubectl patch pvc <PVC_NAME> -p '{"spec":{"resources":{"requests":{"storage":"200Gi"}}}}'
# MCP (preferred)
patch_k8s_resource(parent="...", resourceType="persistentvolumeclaim", name="<PVC_NAME>",
  patch='{"spec":{"resources":{"requests":{"storage":"200Gi"}}}}')

Kubernetes automatically resizes the filesystem.

Best Practices

  1. Always enable volume expansion: Set allowVolumeExpansion: true on all StorageClasses
  2. Use regional PDs for production: replication-type: regional-pd replicates across 2 zones for HA
  3. Use WaitForFirstConsumer: Ensures the PV is provisioned in the same zone as the pod
  4. Choose the right disk type: pd-ssd for databases, pd-balanced (golden path default) for general use, pd-standard for cold storage
  5. Use Filestore for shared access: When multiple pods need to read/write the same files
  6. Use GCS FUSE for data pipelines: Mount buckets directly for ML training data, logs, etc.
  7. Back up PVCs: Use Backup for GKE (see the gke-backup-dr skill) to protect persistent data
Files1
1 files · 11.1 KB

Select a file to preview

Overall Score

86/100

Grade

A

Excellent

Safety

92

Quality

85

Clarity

84

Completeness

80

Summary

This skill provides reference documentation and practical guidance for managing storage in Google Kubernetes Engine (GKE) clusters. It covers persistent disk (PD) configuration, Filestore for shared NFS access, GCS FUSE integration, and best practices for production storage—including StorageClass configuration, PersistentVolumeClaim (PVC) creation, and volume expansion. The skill teaches when to use each storage driver and provides copy-paste YAML templates for common scenarios.

Detected Capabilities

kubernetes manifest guidanceread kubernetes resourcesapply kubernetes manifestsdescribe kubernetes resourcescluster introspection

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

gke storage setuppersistent volumesgcs fuse mountfilestore nfspvc creationstorage class configvolume expansion

Referenced Domains

External domains referenced in skill content, detected by static analysis.

www.apache.org

Use Cases

  • Configure GKE persistent storage with appropriate disk types
  • Set up shared NFS volumes for multi-pod workloads
  • Mount GCS buckets directly using FUSE CSI
  • Expand existing PersistentVolumes without downtime
  • Choose between block storage and file storage based on workload requirements
  • Enable high-availability regional replication for production databases

Quality Notes

  • Strong practical reference with clear tables comparing storage drivers and their use cases
  • Includes copy-paste YAML templates for all major storage patterns (block, shared NFS, GCS FUSE)
  • Clearly documents MCP tool usage for Kubernetes operations
  • Well-organized with golden path defaults and best practices clearly marked
  • Helpful callout about Workload Identity requirements for GCS FUSE
  • Scope boundaries are well-defined: explicitly excludes database replication strategies outside volume provisioning
  • Best practices section covers critical production concerns (regional replication, volume expansion, backups)
  • Minor: could benefit from troubleshooting section for common PVC provisioning failures
Model: claude-haiku-4-5-20251001Analyzed: Jun 29, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v1.1

    Content updated

    ✦ AINo behavioral changes detected.

    2026-06-28

    Latest
  2. v1.0

    2026-06-24

    View This VersionInitial version

Use google/gke-storage in your dev environment

Command Palette

Search for a command to run...