From 5600c3588e331051010517a72fbfad6326b506c7 Mon Sep 17 00:00:00 2001 From: Ricard Bejarano Date: Tue, 6 Oct 2020 02:44:06 +0200 Subject: [PATCH] added comment to clarify that the already-base64-encoded Ceph key must be base64-encoded again when using Kubernetes Secrets, or else use 'stringData' inplace of 'data' --- volumes/cephfs/secret/ceph-secret.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/volumes/cephfs/secret/ceph-secret.yaml b/volumes/cephfs/secret/ceph-secret.yaml index e29a5535a..711614b53 100644 --- a/volumes/cephfs/secret/ceph-secret.yaml +++ b/volumes/cephfs/secret/ceph-secret.yaml @@ -3,4 +3,4 @@ kind: Secret metadata: name: ceph-secret data: - key: QVFCMTZWMVZvRjVtRXhBQTVrQ1FzN2JCajhWVUxSdzI2Qzg0SEE9PQ== + key: QVFCMTZWMVZvRjVtRXhBQTVrQ1FzN2JCajhWVUxSdzI2Qzg0SEE9PQ== # the base64-encoded string of the already-base64-encoded key `ceph auth get-key` outputs