Description

As per we should be able to specify the replica set shared key with secrets.key attribute. However the following is reported:

 

Full cr.yaml:

 

The workaround is to create the Secret with hard-coded name `my-cluster-name-mongodb-keyfile` before deploying the cr.yaml but that is not ideal

Environment

None

Activity

Show:

Pavel Tankov November 1, 2024 at 7:19 AM

So, I tried this: I uncommented the keyFile: my-cluster-name-mongodb-keyfile option and deployed a new psmdb from scratch

and operator log:

Pavel Tankov November 1, 2024 at 7:19 AM

So, we have the option keyFile: my-cluster-name-mongodb-keyfile, which is commented out by default. The value my-cluster-name-mongodb-keyfile is the default one, which means, if I uncomment that line and leave the default value, re-apply cr.yaml, nothing would change, correct? If so, then why does my psmdb deployment enter error state?

Slava Sarzhan October 3, 2024 at 1:57 PM
Edited

The new option was added:

QA: We need to try set the custom one and connect to the components using keyfile (sharding and not sharding deployment)

Slava Sarzhan August 2, 2024 at 3:35 PM

The operator does not support spec.secrets.key: my-cluster-name-keyfile at all We need to add this option.
For developers: It is better to use spec.secrets.keyFile name.

Ivan Groenewold August 2, 2024 at 3:12 PM

Hi Slava, yes I tested with those options and auto-generation works. However as per we should be able to provide the secret name as part of cr.yaml. This is not working

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

dmitriy.kostiuk

Reporter

Ivan Groenewold

Labels

Needs QA

Yes

Needs Doc

Yes

Story Points

1

Sprint

None

Fix versions

Priority

Smart Checklist

Created July 29, 2024 at 3:16 PM
Updated November 14, 2024 at 5:21 PM
Resolved November 11, 2024 at 1:38 PM
Loading...