Update content/en/docs/concepts/storage/dynamic-provisioning.md
Co-authored-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
parent
df4e3e1c11
commit
5aca46b3d0
|
@ -119,7 +119,7 @@ When a default `StorageClass` exists in a cluster and a user creates a
|
||||||
`DefaultStorageClass` admission controller automatically adds the
|
`DefaultStorageClass` admission controller automatically adds the
|
||||||
`storageClassName` field pointing to the default storage class.
|
`storageClassName` field pointing to the default storage class.
|
||||||
|
|
||||||
Note that If you set the `storageclass.kubernetes.io/is-default-class`
|
Note that if you set the `storageclass.kubernetes.io/is-default-class`
|
||||||
annotation to true on more than one StorageClass in your cluster, and you then
|
annotation to true on more than one StorageClass in your cluster, and you then
|
||||||
create a `PersistentVolumeClaim` with no `storageClassName` set, Kubernetes
|
create a `PersistentVolumeClaim` with no `storageClassName` set, Kubernetes
|
||||||
uses the most recently created default StorageClass.
|
uses the most recently created default StorageClass.
|
||||||
|
|
Loading…
Reference in New Issue