Fix 404 issues

pull/23993/head
Feruzjon Muyassarov 2020-09-19 00:07:30 +03:00
parent 3f8a10f9a8
commit 55d2702f3f
No known key found for this signature in database
GPG Key ID: 39AF575CC1CF7F20
1 changed files with 2 additions and 2 deletions

View File

@ -92,7 +92,7 @@ Conceptually, CSI ephemeral volumes are similar to `configMap`,
scheduled onto a node. Kubernetes has no concept of rescheduling Pods scheduled onto a node. Kubernetes has no concept of rescheduling Pods
anymore at this stage. Volume creation has to be unlikely to fail, anymore at this stage. Volume creation has to be unlikely to fail,
otherwise Pod startup gets stuck. In particular, [storage capacity otherwise Pod startup gets stuck. In particular, [storage capacity
aware Pod scheduling](/docs/concepts/storage-capacity/) is *not* aware Pod scheduling](/docs/concepts/storage/storage-capacity/) is *not*
supported for these volumes. They are currently also not covered by supported for these volumes. They are currently also not covered by
the storage resource usage limits of a Pod, because that is something the storage resource usage limits of a Pod, because that is something
that kubelet can only enforce for storage that it manages itself. that kubelet can only enforce for storage that it manages itself.
@ -147,7 +147,7 @@ flexible:
([snapshotting](/docs/concepts/storage/volume-snapshots/), ([snapshotting](/docs/concepts/storage/volume-snapshots/),
[cloning](/docs/concepts/storage/volume-pvc-datasource/), [cloning](/docs/concepts/storage/volume-pvc-datasource/),
[resizing](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims), [resizing](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims),
and [storage capacity tracking](/docs/concepts/storage-capacity/). and [storage capacity tracking](/docs/concepts/storage/storage-capacity/).
Example: Example: