Merge pull request #22108 from pjhwa/fix-22107
Fix issue with links to wrong section name
This commit is contained in:
@@ -41,7 +41,7 @@ be updated once they are created.
|
|||||||
|
|
||||||
Administrators can specify a default StorageClass just for PVCs that don't
|
Administrators can specify a default StorageClass just for PVCs that don't
|
||||||
request any particular class to bind to: see the
|
request any particular class to bind to: see the
|
||||||
[PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#class-1)
|
[PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)
|
||||||
for details.
|
for details.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
|
|||||||
@@ -24,7 +24,7 @@ Depending on the installation method, your Kubernetes cluster may be deployed wi
|
|||||||
an existing StorageClass that is marked as default. This default StorageClass
|
an existing StorageClass that is marked as default. This default StorageClass
|
||||||
is then used to dynamically provision storage for PersistentVolumeClaims
|
is then used to dynamically provision storage for PersistentVolumeClaims
|
||||||
that do not require any specific storage class. See
|
that do not require any specific storage class. See
|
||||||
[PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#class-1)
|
[PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)
|
||||||
for details.
|
for details.
|
||||||
|
|
||||||
The pre-installed default StorageClass may not fit well with your expected workload;
|
The pre-installed default StorageClass may not fit well with your expected workload;
|
||||||
|
|||||||
Reference in New Issue
Block a user