Issues

[BUG] Unexpected resource creation when the MongoDB CR is already deleted

[BUG] Mongodb operator does not delete PVC after scaling-down leading to resource leak

[BUG] ssl-internal certificate and secret never gets created if crash happens at some particular point

[BUG] ssl-internal secret never gets created if the operator crashes and restarts at some particular point

Can't reduce replicaset size with delete psmdb and cluster re-creation

TLS Mode -

[BUG] Redundant deletion by issuing `Delete` without checking resource existence

[BUG] Arbiter statefulset gets mistakenly deleted when reading stale `replset.arbiter.enabled`

Labels are not inherited by PVCs

Mongos pods don't show custom labels

[BUG] Nil pointer dereference when setting `spec.sharding.enabled` from false to true

[BUG] Config statefulset gets mistakenly deleted when reading stale `spec.sharding.enabled`

Cluster Wide Scope for Operator Deployment (WATCH_NAMESPACE)

remove files from S3 for on-demand/manual backup

[BUG] Stale deletionTimestamp information leads to undesired statefulset and PVC deletion

version service check is pinging old version after upgrade

SmartUpdate with arbiter doesn't work

operator should check if balancer running before starting the restore process

arbiter - add possibility to specify custom memory/cpu requirements

test database is marked as a system database

operator tries to add shard repeatedly even when already added when arbiters used

Add logic for syncing restore with mongos

running multiple replica sets without sharding enabled should be prohibited

error status when using arbiter in replica set

mongos fails when allowUnsafeConfiguration=true and without TLS enabled

wrong cluster status after unsuccessful shard removal

disabling or enabling sharding with two or more shards should not be allowed

sharding - The server certificate does not match the remote host name

shard never removed without clear reason in the logs

PSMDB object status showing shard after successful removal

sporadic missing of shards on cluster init