commit
0c289b6abf
|
@ -54,7 +54,7 @@ dynamic provisioning for themselves.
|
|||
To enable dynamic storage provisioning based on storage class, the cluster administrator
|
||||
needs to enable the `DefaultStorageClass` [admission controller](/docs/admin/admission-controllers/#defaultstorageclass)
|
||||
on the API server. This can be done, for example, by ensuring that `DefaultStorageClass` is
|
||||
among the comma-delimited, ordered list of values for the `--admission-control` flag of
|
||||
among the comma-delimited, ordered list of values for the `--admission-control` flag of
|
||||
the API server component. For more information on API server command line flags,
|
||||
please check [kube-apiserver](/docs/admin/kube-apiserver/) documentation.
|
||||
|
||||
|
@ -417,8 +417,6 @@ spec:
|
|||
|
||||
`PersistentVolumes` binds are exclusive, and since `PersistentVolumeClaims` are namespaced objects, mounting claims with "Many" modes (`ROX`, `RWX`) is only possible within one namespace.
|
||||
|
||||
``
|
||||
|
||||
## Writing Portable Configuration
|
||||
|
||||
If you're writing configuration templates or examples that run on a wide range of clusters
|
||||
|
@ -455,4 +453,3 @@ and need persistent storage, we recommend that you use the following pattern:
|
|||
default.
|
||||
At some point, the alpha annotation will cease to have meaning, but the unset
|
||||
`storageClass` field on the PVC will have the desired effect.
|
||||
|
||||
|
|
Loading…
Reference in New Issue