From 338b404bfd0c741bf633a72417b329f6e076d01e Mon Sep 17 00:00:00 2001 From: "David J. M. Karlsen" Date: Mon, 24 Sep 2018 01:16:05 +0200 Subject: [PATCH] Fix invalid claim name Signed-off-by: David J. M. Karlsen --- design/dynamic-provision-filesystem.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/design/dynamic-provision-filesystem.md b/design/dynamic-provision-filesystem.md index 23c289673..27c4d78e3 100644 --- a/design/dynamic-provision-filesystem.md +++ b/design/dynamic-provision-filesystem.md @@ -59,7 +59,7 @@ To create a filesystem, you just create a PVC object. This is consistent with al apiVersion: v1 kind: PersistentVolumeClaim metadata: - name: myfsData + name: myfsdata spec: storageClassName: rook-filesystem-simple path: /myData # Will use root path, "/", if not provided @@ -94,7 +94,7 @@ spec: volumes: - name: mysql-persistent-storage persistentVolumeClaim: - claimName: myfsData + claimName: myfsdata ``` Note that the consuming pod manifest looks the same whether it is mounting a filesystem or a block device.