Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. MongoDB CR should support topologySpreadConstraints

    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

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  2. To setup number of backup daemons in ops-manager.yaml

    In ops-manager.yaml, can we define the number of the initial backup daemons?

    4 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow customizing mongod port in kubernetes

    The additionalMongodConfig feature was a great addition to the Operator.

    Setting the spec.additionalMongodConfig.net.port to a value other than the default 27017 is not working as expected. The default port is still used despite the custom port value appearing in the MongoDB resource description/manifest. A common security compliance checklist often includes running services on non-default ports.

    Please consider allowing the net.port to be set to a custom value; this may have implications with the services that are automatically created in the cluster.

    1 vote
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  4. 13 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  5. adminCredentials secret should always be source of truth for OpsManager

    The secret is only taken into account by OpsManager initially when OpsManager is deployed. As soon as the password of this user is changed in OpsManager, this secret is out of sync.

    From the docs: "Use these credentials to log in to Ops Manager for the first time. Once Ops Manager is deployed, you should change the password or remove this secret."
    https://docs.mongodb.com/kubernetes-operator/v1.4/tutorial/plan-om-resource/#prerequisites

    Option 1: This secret should be in-sync with the OpsManager database. Preferably the sync should be from the k8s secret to the OpsManager database.

    Option 2: Create a CRD "MongoDBOpsManagerUser" that handles User/Password management for OpsManager similar…

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support Arbiters with MongoDB Kubernetes Operator

    Support arbiters with MongoDB Kubernetes Operator so that Replicasets should be deployed in PSA configuration.

    9 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show Kubernetes resources in Ops Manager

    Show some of the Kubernetes resources in Ops Manager
    1. show namespaces in projects,
    2. Show list of resources in cluster view

    5 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  8. 7 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add Backup configuration to MongoDB Custom Resource

    Allow configuration of backup settings in MongoDB Custom resource.
    This includes management of backed up resources when updating, moving or deleting clusters

    8 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →

    We are going to address this later in July-August.
    When Backup configuration is straight forward, workflow around deleting or modifying it is a bit more complicated. We Would like to get it right.

  10. Kubernetes Operator: Ops Manager backup infrastructure automated removal

    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

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support Helm Chart for operator

    Provide Helm charts for MongoDB Enterprise operator

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base