[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["# Using SSD persistent disks\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page explains how to create dynamic [PersistentVolume](/kubernetes-engine/docs/concepts/persistent-volumes)\nresources that are backed by [SSD persistent disks](/compute/docs/disks).\n\nSSD persistent disks\n--------------------\n\nBy default, [dynamically provisioned PersistentVolumes](/kubernetes-engine/docs/concepts/persistent-volumes#dynamic_provisioning)\nuse the [default `StorageClass`](/kubernetes-engine/docs/concepts/persistent-volumes#storageclasses)\nand are backed by standard hard disks. If you need faster SSDs, you can use the\n`premium-rwo` storage class from the [Compute Engine persistent disk CSI Driver](/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver)\nto provision your volumes. This can be done by setting the `storageClassName`\nfield to `premium-rwo` in your `PersistentVolumeClaim` as shown in the following\nexample: \n\n # ssd-claim.yaml\n apiVersion: v1\n kind: PersistentVolumeClaim\n metadata:\n name: my-volume\n spec:\n storageClassName: premium-rwo\n accessModes:\n - ReadWriteOnce\n resources:\n requests:\n storage: 30Gi\n\nTo create the `my-volume` PersistentVolumeClaim object, use the following\n`kubectl apply` command: \n\n kubectl apply -f ssd-claim.yaml\n\nWhen you create this `PersistentVolumeClaim` object with `kubectl apply`,\nKubernetes dynamically creates a corresponding `PersistentVolume` object."]]