Data at rest encryption - Percona Operator for MongoDB

MongoDB Percona Distribution for MongoDB
1

According to Data at rest encryption - Percona Operator for MongoDB I can set my encryption secret as a Kubernetes secrets file.

But what name must the stored Key be called the docs don’t tell.

Getting:

{"t":{"$date":"2023-01-21T16:15:35.362+00:00"},"s":"E",  "c":"STORAGE",  "id":29038,   "ctx":"initandlisten","msg":"Exception in EncryptionKeyDB::init: {e}","attr":{"e":"cannot read stats of encryption key file: /etc/mongodb-encryption/encryption-key: No such file or directory"}}
{"t":{"$date":"2023-01-21T16:15:35.362+00:00"},"s":"E",  "c":"CONTROL",  "id":20558,   "ctx":"initandlisten","msg":"std::exception in initAndListen, terminating","attr":{"error":"cannot read stats of encryption key file: /etc/mongodb-encryption/encryption-key: No such file or directory"}}

Thanks for looking into this and updating docs.

1 Like
2

Ok, key name seems to be:

encryption-key in the secrets file.

It expects a base64 encoded value and the you can create --from-literal to let it be encoded another time as usual by kubectl.

PRs needed for docs and helm chart Readme file.

1 Like