From cd0f4a2526ea86a96a4f4ae9fa14f0c481fda75f Mon Sep 17 00:00:00 2001 From: Kaitlyn Barnard Date: Tue, 17 Apr 2018 16:54:59 -0400 Subject: [PATCH] Link fixes to CSI blog post (#8058) * adding CSI blog post * update images * fixing images * link changes * fixing images * link update * resolving merge conflict --- blog/_posts/2018-04-10-container-storage-interface-beta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/_posts/2018-04-10-container-storage-interface-beta.md b/blog/_posts/2018-04-10-container-storage-interface-beta.md index 1606ea847a..6636d5e90d 100644 --- a/blog/_posts/2018-04-10-container-storage-interface-beta.md +++ b/blog/_posts/2018-04-10-container-storage-interface-beta.md @@ -177,7 +177,7 @@ In addition to being difficult to deploy, Flex did not address the pain of plugi CSI addresses these issues by not only enabling storage plugins to be developed out-of-tree, but also containerized and deployed via standard Kubernetes primitives. -If you still have questions about in-tree volumes vs CSI vs Flex, please see the [Volume Plugin FAQ] (https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md). +If you still have questions about in-tree volumes vs CSI vs Flex, please see the [Volume Plugin FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md). ## What will happen to the in-tree volume plugins?