All work

setFCV option doesn't change version in replica set major upgrade

Document - new feature - major version upgrade

Document - new feature - store custom configuration in Secrets and ConfigMaps

Allow storing custom configuration in ConfigMaps

Allow storing custom configuration in Secrets

Custom configuration - new section in cr.yaml - mongos

Document - new feature - recover from S3 directly

cannot run 2 nodes and arbiter as per docs

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

Labels are not inherited by PVCs

Set imagePullPolicy for init container

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

Add PMM client sidecar for HAProxy pods

Mongos fail when name field is empty in configsvrReplSet section of CR

Remove mongos.expose.enabled from Custom Resource

Fix one-pod e2e test

Unpause of a cluster doen't work with enabled replsets expose set to LB

Add annotations to backup cron jobs

Delete Secret object in Kubernetes if pvc finalizer is enabled

Add OpenAPI validation to CRD

Improve Concurrent Jobs Check Using PBM Locks

serviceAnnotations is not updated on cr.yaml change

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

Handle out of disk space situations

arbiter - add possibility to specify custom memory/cpu requirements

Add support for Workload Identity authentication for backup to GCS buckets

test database is marked as a system database

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

Deployment of a new cluster fails, but only sometimes

Add logic for syncing restore with mongos

Fix some typos in comments/messages

running multiple replica sets without sharding enabled should be prohibited

error status when using arbiter in replica set

Simplify secret change logic

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

Document - how to install through Red Hat marketplace

[documentation] On the Update page, the patch command has an extra } that causes invalid JSON error

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