From 65a50f2b4ad279f51e9704ee3190143d0dd2f8d5 Mon Sep 17 00:00:00 2001 From: mickymiek Date: Wed, 19 Dec 2018 15:38:18 +0100 Subject: [PATCH] edit cephfs docs --- docs/deploy-cephfs.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/deploy-cephfs.md b/docs/deploy-cephfs.md index 952e9f2c1..0d1e1f17f 100644 --- a/docs/deploy-cephfs.md +++ b/docs/deploy-cephfs.md @@ -26,6 +26,7 @@ Option | Default value | Description `--drivername` | `csi-cephfsplugin` | name of the driver (Kubernetes: `provisioner` field in StorageClass must correspond to this value) `--nodeid` | _empty_ | This node's ID `--volumemounter` | _empty_ | default volume mounter. Available options are `kernel` and `fuse`. This is the mount method used if volume parameters don't specify otherwise. If left unspecified, the driver will first probe for `ceph-fuse` in system's path and will choose Ceph kernel client if probing failed. +`--metadatastorage` | _empty_ | Whether should metadata be kept on node as file or in a k8s configmap (`node` or `k8s_configmap`) **Available environmental variables:** `KUBERNETES_CONFIG_PATH`: if you use `k8s_configmap` as metadata store, specify the path of your k8s config file (if not specified, the plugin will assume you're running it inside a k8s cluster and find the config itself).