This page explains how to create dynamic [PersistentVolume](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes.md.txt)
resources that are backed by [SSD persistent disks](https://docs.cloud.google.com/compute/docs/disks.md.txt).

## SSD persistent disks

By default, [dynamically provisioned PersistentVolumes](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes.md.txt#dynamic_provisioning)
use the [default `StorageClass`](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes.md.txt#storageclasses)
and are backed by standard hard disks. If you need faster SSDs, you can use the
`premium-rwo` storage class from the [Compute Engine persistent disk CSI Driver](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver.md.txt)
to provision your volumes. This can be done by setting the `storageClassName`
field to `premium-rwo` in your `PersistentVolumeClaim` as shown in the following
example:

```yaml
# ssd-claim.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-volume
spec:
  storageClassName: premium-rwo
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 30Gi
```

To create the `my-volume` PersistentVolumeClaim object, use the following
`kubectl apply` command:

```bash
kubectl apply -f ssd-claim.yaml
```

When you create this `PersistentVolumeClaim` object with `kubectl apply`,
Kubernetes dynamically creates a corresponding `PersistentVolume` object.