GKE Persistent Storage with GCE PDs
You'll learn how Google Kubernetes Engine uses Google Compute Engine Persistent Disks to provide durable storage for your containerized applications.
What Are GCE Persistent Disks?
Google Compute Engine Persistent Disks (GCE PDs) are the default storage backend for persistent volumes in GKE. Think of them as external hard drives that can be attached to your pods—when a pod restarts or moves to a different node, the same disk reattaches, preserving your data.
How GKE Uses Storage Classes
GKE comes with pre-configured StorageClasses that define different types of GCE PDs:
standard-rwo: Standard persistent disks (HDD-backed)pd-balanced: Balanced persistent disks (SSD performance at lower cost)pd-ssd: High-performance SSD persistent disks
When you create a PersistentVolumeClaim (PVC) referencing a StorageClass, GKE automatically provisions the appropriate GCE PD—this is dynamic provisioning in action.
Dynamic Provisioning in Practice
Instead of manually creating disks in the Google Cloud Console, you simply declare what storage you need in your PVC. GKE's storage controller sees the request, creates the GCE PD automatically, formats it, and binds it to your PVC. When you delete the PVC, the disk can be retained or deleted based on the StorageClass's reclaim policy.
This automation means developers don't need to manage infrastructure—they just request storage, and GKE handles the rest. The disks are zonal by default (though regional options exist), meaning they live in the same zone as your nodes for optimal performance.
Key Takeaway: GKE uses GCE Persistent Disks as the foundation for persistent storage, with StorageClasses enabling dynamic provisioning so you can request storage declaratively without manually creating infrastructure.