Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. MongoDB Operator Deployment Env Variables Push Down

    This is a feature request to have custom environment variables, configured in the MongoDB Operator's Deployment manifest, push down or propagate to all resources created by the Operator.

    For example, it may be desired to add environment variables with context. A more specific example could include setting a TZ timezone environment variable that is automatically added to all pod containers created by the Operator.

    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

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

    32 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

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

  3. sharding

    Should provide sharding feature in community Operator.

    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

    1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  4. Ops Manager and Backup infrastracture Disaster Recovery support with K8s Operator

    We have carried out tests with MongoDB v1.5.5 K8s Operator and Ops Manager 4.2.18 with Backup infrastructure (S3 Snapshots) in an Openshift 3.11 environment (MongoDB Support case attached).

    In this case, a "Disaster Recovery" simulation has been carried out. However, several components created by the Operator had to be restored to obtain a similar state to the one before the "disaster".

    Furthermore, it is very likely that the S3 Snapshots will be lost if the process is not completed in a certain manner.

    It would be great to have an official approach to deploy/restore an OM resource using MongoDB K8s…

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  5. Manage indexes creation and sharding of collections in a GitOps way

    We're developing a Microservices-based product that is based on MongoDB and Kafka. In this context, we're currently aiming at implementing most of our DevOps-related activities in a GitOps way. Setup, rolling upgrades and scaling the number of replicas can be achieved with the Operator today, but it would be great also if activities like index creation and sharding of collections could be done via the Operator.

    A similar approach has been taken for Kafka, where cluster installation, rolling upgrades and scaling out is handed by the operator (Strimzi), but also topic management: https://strimzi.io/docs/operators/latest/overview.html#overview-concepts-topic-operator-str

    We have developed an internal tool to…

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  6. Manage the MongoDB Agent functions using the operator

    Currently, the operator does not enable backup function for AppDB, but it does enable monitoring. For everything else (non-AppDB) the operator does enable the Backup and Monitoring functions, even if backup is not configured

    At the moment none of these functions are configurable with the Operator. The only method to disable the Backup or Monitoring function is through the Ops Manager UI.

    Requesting the ability to manage the functions through the operator.

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow to pin specific MongoDB Agent version to be used

    What is the problem that needs to be solved? In some rare situations where upgrade of Cloud Manager's MongoDB Agent to the latest version leads to Golang panic (or any other critical issue) there's no way for Cloud Manager user to rollback MongoDB Agent version in case if this environment is running in Kubernetes Operator. The script which launch MongoDB Agent is using the latest version from Cloud Manager Project, without any option to change it other then editing the script itself which is not possible in Kubernetes pod.

    Why is it a problem? (the pain) If after Cloud Manager's…

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support kubernetes taints and tolerations

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

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  9. Assignment labels in YAML for Snapshot storage

    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

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add ability to configure Pod Disruption Budget for STS

    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.

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  11. Operator automatically provision an Ops Manager programmatic API key

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

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow using other port than 8080 (or 8443) when deploy Ops Manager

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

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  13. 1 vote

    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

    1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  14. Build a course for Mongo Univesity

    Please, build a course like you already have but now for Kubernetes Operator. I had serious troubles implementing it.

    6 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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  15. Create AppDB user with backup role to allow execution of mongodump

    For the purpose of regularly performing backups of the AppDB using mongodump --oplog.

    3 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

    under review  ·  1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  16. Pin versions for all images in values file

    currently for release 1.9.0, the helm chart has no way to explicitly use a specific version of the following images:
    - mongodb-enterprise-ops-manager
    - mongodb-enterprise-appdb

    This is not ideal and hard to scale in the enterprise. Request the ability to pin versions to all images from values file.

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow the Kubernetes Operator to delete a project

    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.

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  18. Headless OPS Manager deployment

    Currently Ops Manager CRD deployment requires configuration using GUI which is a manual step. An option completely define all OPS Manager settings / Org in declarative manner via yaml will be great in building completely automated CI/CD Pipelines

    9 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 →
  19. Ops Manager LDAP Auth using kubernetes manifest

    Currently, there is no way to enable LDAP Auth for the Ops Manager Users on my kubernetes Ops Manager pods using manifests.

    This essentially means that one would not be able to use LDAP and ci/cd simultaneously with Ops Manager with the enterprise kubernetes operator.

    Mongodb enterprise support has confirmed that in the event of disaster recovery or a deployment of a new cluster, manual steps must be done to enable LDAP during a ci/cd deployment.

    It should not be expected to sign in and manually do anything in a web gui in an enterprise solution. It is simply not…

    1 vote

    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

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  20. Pin image tags in Enterprise Kubernetes Operator values file

    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.

    1 vote

    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

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

Feedback and Knowledge Base