Merge pull request #44942 from tamilselvan1102/k8s-doc-web-20240130
Information about default StorageClasses
This commit is contained in:
commit
6479f0172f
|
|
@ -119,9 +119,10 @@ 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 there can be at most one *default* storage class on a cluster, or
|
Note that if you set the `storageclass.kubernetes.io/is-default-class`
|
||||||
a `PersistentVolumeClaim` without `storageClassName` explicitly specified cannot
|
annotation to true on more than one StorageClass in your cluster, and you then
|
||||||
be created.
|
create a `PersistentVolumeClaim` with no `storageClassName` set, Kubernetes
|
||||||
|
uses the most recently created default StorageClass.
|
||||||
|
|
||||||
## Topology Awareness
|
## Topology Awareness
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue