Well I just upgraded the operator helm’s version as the documentation says, then the crVersion of the psmdb custom resource object. Jumped from 1.18.0 to 1.19.0 in both.
MongoDB itself image version is percona-server-mongodb:6.0.19-16
Status is shown as ‘ready’, but the error message from the operator keep spamming:
"error": "write status: PerconaServerMongoDB.psmdb.percona.com \"test-mongodb\" is invalid: [status.replsets.cfg.members: Invalid value: \"object\": replsets.cfg.members in body must be of type array: \"object\", status.replsets.shard01.members: Invalid value: \"object\": replsets.shard01.members in body must be of type array: \"object\"]"
When I start up the operator it shows in the logs this:
{"level":"info","ts":1738328924.249747,"logger":"KubeAPIWarningLogger","msg":"unknown field \"status.replsets.cfg.members.test-mongodb-cfg-0\""}
{"level":"info","ts":1738328924.2497528,"logger":"KubeAPIWarningLogger","msg":"unknown field \"status.replsets.cfg.members.test-mongodb-cfg-1\""}
{"level":"info","ts":1738328924.249755,"logger":"KubeAPIWarningLogger","msg":"unknown field \"status.replsets.cfg.members.test-mongodb-cfg-2\""}
{"level":"info","ts":1738328924.2497606,"logger":"KubeAPIWarningLogger","msg":"unknown field \"status.replsets.shard01.members.test-mongodb-shard01-0\""}
{"level":"info","ts":1738328924.2497625,"logger":"KubeAPIWarningLogger","msg":"unknown field \"status.replsets.shard01.members.test-mongodb-shard01-1\""}
{"level":"info","ts":1738328924.2497704,"logger":"KubeAPIWarningLogger","msg":"unknown field \"status.replsets.shard01.members.test-mongodb-shard01-2\""}