Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Introduce Helm Chart for MongoDB, MongoDBUser and secrets

    Provide a helm chart that deploys MongoDB, MongoDBUser, secrets and all other resources needed.

    The goal is to simplify the deployment of a MongoDB instance and everything that comes with it down to a helm one-liner.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  2 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  3. Binaries should be provided via Docker images

    To implement this in a Kubernetes native way for offline deployments, the binaries should be provided as Docker images and distributed through the Docker repositories that are already present in the k8s environment.

    Option 1 (intermediate): Allow Mount of Docker images in the MongoDBOpsManager resource for the path defined in automation.versions.directory. This would allow us to pre-package the binaries needed and bring up the OpsManager in a kubernetes native way. Everything else (e.g. agent downloading the tgz) would stay the same and still be the "OpsManger-way".

    Option 2 (long term): The MongoDB TGZ package is provided as Docker image by…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  5. mongocli feature request: whitelist with timeout on current ip to allow temporary mongoshell access from temporary locations

    Please add a timeout parameter to the mongocli whitelist command.
    Presently, we have to login via web browser to enable temporary mongoshell access from temporary locations.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base