From 55d2702f3fd02389e68e7a55ea31fb1cb8f86bec Mon Sep 17 00:00:00 2001 From: Feruzjon Muyassarov Date: Sat, 19 Sep 2020 00:07:30 +0300 Subject: [PATCH] Fix 404 issues --- content/en/docs/concepts/storage/ephemeral-volumes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/storage/ephemeral-volumes.md b/content/en/docs/concepts/storage/ephemeral-volumes.md index 450c258614..e4831cfd16 100644 --- a/content/en/docs/concepts/storage/ephemeral-volumes.md +++ b/content/en/docs/concepts/storage/ephemeral-volumes.md @@ -92,7 +92,7 @@ Conceptually, CSI ephemeral volumes are similar to `configMap`, scheduled onto a node. Kubernetes has no concept of rescheduling Pods anymore at this stage. Volume creation has to be unlikely to fail, 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 the storage resource usage limits of a Pod, because that is something that kubelet can only enforce for storage that it manages itself. @@ -147,7 +147,7 @@ flexible: ([snapshotting](/docs/concepts/storage/volume-snapshots/), [cloning](/docs/concepts/storage/volume-pvc-datasource/), [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: