As PodAntiAffinity does not really give enough flexibility in achieving High Availability and enforcing distribution across nodes, it should be possible to add topologySpreadConstraints to the podSpec (of both ShardedCluster and other deployment types). As of now topologySpreadConstraints are ignored by the Operator.

https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#comparison-with-podaffinity-podantiaffinity

MongoDB Kubernetes Operator can manage OpsManager Resources including Backup infrastructure.
When Users want to disable backup infrastructure, the Operator does not remove BackupDeamon Stateful set or disables the backup configuration.
This request is to make Operator clean up Backup configuration for OpsManager and delete K8S resources as well reconfigure OpsManager

Provide Helm charts for MongoDB Enterprise operator

With Ops Manager Local Mode on Kubernetes, the version manifest is required to be updated manually via UI or API.

It would be the best practice to support updating version manifest using a command to the Operator or OM Pods.

To be able to have MongoDB logs redirect to stdout and this having it into GKE CloudLogs, we should NOT configure a systemLog.destination nor a systemLog.path.

In 0.6.0 release, systemLog.destination and path are hardcoded and cannot be nullable.

see automationconfigbuilder.go at line 208:

...
process.SetSystemLog(SystemLog{
Destination: "file",
Path: path.Join(DefaultAgentLogPath, "/mongodb.log"),
})
...

Hello,
Is there a way to migrate existing non-kubernetes MongoDB clusters to MongoDB Kubernetes Operator?

I believe kubernetes taints and tolerations are not supported by the operator, yet I find it a much needed capability.

Currently, if you want to assign a snapshot store to a certain project, it is required to access the Admin view and configure the "Assignment Labels" property under Backup > Snapshot Storage with the name of the corresponding project.

AFAIK, it is not possible to assign this configuration in the Ops Manager's YAML. E.g.:

s3Stores:

- mongodbResourceRef:

    name: s3-metadata-db

  mongodbUserRef:

    name: s3-meta-store-user

  name: s3store1

  pathStyleAccessEnabled: false

  s3BucketEndpoint: endpoint1.corp

  s3BucketName: backup1-bucket

  s3SecretRef:

    name: s3-credentials

- mongodbResourceRef:

    name: s3-metadata-db

  mongodbUserRef:

    name: s3-meta-store-user

  name: s3store2

  pathStyleAccessEnabled: false

  s3BucketEndpoint: backup2.corp

  s3BucketName: backup2-bucket

  s3SecretRef:

    name: second-credentials

During maintenance work EKS admins may need to evict nodes. This should not cause outage for MongoDB cluster/replicaset running on these nodes. we can create manually PDB for STS, but it would be nice to have an option to do it as part of MongoDB Kubernetes Operator.

Operator automatically provision an Ops Manager programmatic API key, The current instructions require human intervention to create an AP

The default port is 8080 or 8443 (for https) and cannot be changed

Currently it is not possible to delete a project via kubectl command.

As the Kubernetes Operator allows one to create a project (configmap) and deploy a replica set, we would expect it to also allow the deletion of a project so that we can fully automate the solution.

Should be able to pin tags for images like mongodb-enterprise-appdb in https://github.com/mongodb/mongodb-enterprise-kubernetes/blob/master/helm_chart/values.yaml

Currently, we are forced to use the latest tag, which has caused issues and broke disaster recovery for our project.

If we would have been able to use an older tag of the image, we could have recovered fast. since we were forced to use the latest tag, it took several days to recover. This does not seem acceptable for an enterprise software.

It's still very new and only kube-router is the only "free" one that supports it. But this is great simplify the network configurations to connect to replicas and shards.

Route Sharing is currently supported on Red Hat OpenShift 4.4+