ceph-csi/examples/cephfs/secret.yaml

---
apiVersion: v1
kind: Secret
metadata:
  name: csi-cephfs-secret
  namespace: default
stringData:
  # Required for statically and dynamically provisioned volumes
  userID: <plaintext ID>
  userKey: <Ceph auth key corresponding to ID above>

  # Encryption passphrase
  encryptionPassphrase: test_passphrase
Fix yamllint issues Signed-off-by: Madhu Rajanna <mrajanna@redhat.com> 2019-02-07 09:59:26 +00:00			`---`
added examples 2018-07-18 14:49:15 +00:00			`apiVersion: v1`
			`kind: Secret`
			`metadata:`
			`name: csi-cephfs-secret`
			`namespace: default`
Modify RBD plugin to use a single ID and move the id and key into the secret RBD plugin needs only a single ID to manage images and operations against a pool, mentioned in the storage class. The current scheme of 2 IDs is hence not needed and removed in this commit. Further, unlike CephFS plugin, the RBD plugin splits the user id and the key into the storage class and the secret respectively. Also the parameter name for the key in the secret is noted in the storageclass making it a variant and hampers usability/comprehension. This is also fixed by moving the id and the key to the secret and not retaining the same in the storage class, like CephFS. Fixes #270 Testing done: - Basic PVC creation and mounting Signed-off-by: ShyamsundarR <srangana@redhat.com> 2019-06-01 21:26:42 +00:00			`stringData:`
doc: update documentation for userID and userKey Signed-off-by: Niraj Yadav <niryadav@redhat.com> 2024-12-09 12:24:42 +00:00			`# Required for statically and dynamically provisioned volumes`
Modify RBD plugin to use a single ID and move the id and key into the secret RBD plugin needs only a single ID to manage images and operations against a pool, mentioned in the storage class. The current scheme of 2 IDs is hence not needed and removed in this commit. Further, unlike CephFS plugin, the RBD plugin splits the user id and the key into the storage class and the secret respectively. Also the parameter name for the key in the secret is noted in the storageclass making it a variant and hampers usability/comprehension. This is also fixed by moving the id and the key to the secret and not retaining the same in the storage class, like CephFS. Fixes #270 Testing done: - Basic PVC creation and mounting Signed-off-by: ShyamsundarR <srangana@redhat.com> 2019-06-01 21:26:42 +00:00			`userID: <plaintext ID>`
			`userKey: <Ceph auth key corresponding to ID above>`
added examples 2018-07-18 14:49:15 +00:00
examples: Ceph FS fscrypt / KMS additions Add encryption configuration to Ceph FS examples Signed-off-by: Marcel Lauhoff <marcel.lauhoff@suse.com> 2022-08-19 14:51:49 +00:00			`# Encryption passphrase`
			`encryptionPassphrase: test_passphrase`