doc: make sure configmap object referred or documented correctly

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit is contained in:
Humble Chirammal
2020-06-10 11:53:03 +05:30
committed by mergify[bot]
parent 8b606f538f
commit c1a269191c
8 changed files with 16 additions and 16 deletions

View File

@ -113,7 +113,7 @@ kubectl create -f csi-nodeplugin-psp.yaml
kubectl create -f csi-config-map.yaml
```
The config map deploys an empty CSI configuration that is mounted as a volume
The configmap deploys an empty CSI configuration that is mounted as a volume
within the Ceph CSI plugin pods. To add a specific Ceph clusters configuration
details, refer to [Creating CSI configuration for RBD based
provisioning](../examples/README.md#creating-csi-configuration-for-rbd-based-provisioning)
@ -232,8 +232,8 @@ Configuration must include `encryptionKMSType: "vault"`. In order for ceph-csi
to be able to access the configuration you will need to have it mounted to
csi-rbdplugin containers in both daemonset (so kms client can be instantiated to
encrypt/decrypt volumes) and deployment pods (so kms client can be instantiated
to delete passphrase on volume delete) `ceph-csi-encryption-kms-config` config
map.
to delete passphrase on volume delete) `ceph-csi-encryption-kms-config`
configmap.
> Note: kms configuration must be a map of string values only
> (`map[string]string`) so for numerical and boolean values make sure to put

View File

@ -104,7 +104,7 @@ parameters:
# Use external key management system for encryption passphrases by specifying
# a unique ID matching KMS ConfigMap. The ID is only used for correlation to
# config map entry.
# configmap entry.
encryptionKMSID: <kms-id>
reclaimPolicy: Delete