From d24278918c7ad4cb22d20fa52a1fe69841498bfa Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Thu, 7 Mar 2019 22:00:10 +0000 Subject: [PATCH] Fix broken link (#12717) Resolves #12713 --- content/en/docs/reference/glossary/csi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/glossary/csi.md b/content/en/docs/reference/glossary/csi.md index 29e5550ccf..ae93b120ff 100644 --- a/content/en/docs/reference/glossary/csi.md +++ b/content/en/docs/reference/glossary/csi.md @@ -18,4 +18,4 @@ tags: CSI allows vendors to create custom storage plugins for Kubernetes without adding them to the Kubernetes repository (out-of-tree plugins). To use a CSI driver from a storage provider, you must first [deploy it to your cluster](https://kubernetes-csi.github.io/docs/Setup.html). You will then be able to create a {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} that uses that CSI driver. * [CSI in the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volumes/#csi) -* [List of available CSI drivers](https://kubernetes-csi.github.io/docs/Drivers.html) +* [List of available CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html)