Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Deploy MongoDB across different Kubernetes clusters

    MongoDB Operator can only deploy and manage MongoDB in a single Kubernetes cluster. However, for DR and global apps, it is important to deploy a single DataBase across multiple Kubernetes clusters to allow for DR or globally distributed apps.

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

    We’ll send you updates on this idea

    1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →

    We are going to start POC in July to figure this out. Our goal is to form a single cluster that can fallback between different K8S clusters.

  2. 11 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 →
  3. Automation Agent Client Certification Validation

    Many customers require that the MMS automation agent has a valid x509 for TLS communications with Ops Manager. With the Kubernetes Operator this is not currently possible so these customers cannot use the Operator to deploy MongoDB instances within their environments.

    This feature would improve the security of communications between agents and the Ops Manager and meet the security requirements of many of our customers who cannot move to services like Atlas.

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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

    6 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.

  5. Define current limits of Kubernetes Operator

    > 1.) What is the limiting factor of the Operator? Is it number of Pods, number of Custom Resources (e.g. MongoDB, MongoDBUser) or something else?

    > 2.) What does the number of "Clusters" refer to? Does it differ for Standalone, ReplicaSet and ShardedCluster?

    > 3.) How many instances of the "Clusters" in 2.) are supported per MongoDB Operator?

    Is there any way to add this sort of data to our documentation?

    Thanks

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

    We’ll send you updates on this idea

    1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →

    We are planning to publish a number of recommendations for the most popular cluster sizes and types. ETA is approx September. We will expect the gradual update to our production notes and docs until then

  6. Allow to configure options for automation agent logs

    Currently there is no way in Kubernetes operator to configure how long automation/backup/monitoring agent logs should be stored. they can easily occupy all space in pod.

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

    We’ll send you updates on this idea

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

    Provide Helm charts for MongoDB Enterprise operator

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base