Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow S3 Oplog Store to be defined and configured using the Operator.

    Ops Manager can utilize S3 storage for the Oplog Store. It should be possible to define and configure an S3 Oplog Store from 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. Enable S3 Snapshot Storage via Kubernetes Operator with IAM role

    Configuring an S3 Snapshot Storage with IAM roles is only possible via Ops Manager UI or API.

    It would be great to be able to do this configuration via the 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 →
  3. sharding

    Should provide sharding feature in community Operator.

    4 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

    planned  ·  2 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow disabling Blockstore for assignment through the Ops Manager CRD

    By default, when enabling backups and configuring a Blockstore for an Ops Manager custom object, the specified Blockstore will be set as "Assignment enabled" in the UI.

    It would be helpful to expose the enable/disable button for the blockstore through the CRD since disabling it through the UI, results in the parameter being reverted every time the operator consolidates. This is useful for the case when more than a single store is configured and as a user you would like to disable the blockstore to make it unavailable for new backup jobs.

    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. Provide support to update version manifest to Ops Manager that uses local mode

    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.

    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. Add ability to have systemLog redirected to stdout (just have to remove systemLog.destination and path)

    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"),
    })
    ...

    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 →
  7. Fine-tune RBAC rules for mongodb.com resources

    Right now, the default RBAC rules for the mongodb-enterprise-operator role/clusterrole are:

    apiGroups:
      - mongodb.com
    resources:
      - mongodb
      - mongodb/finalizers
      - mongodb/status
      - mongodbusers
      - mongodbusers/status
      - opsmanagers
      - opsmanagers/finalizers
      - opsmanagers/status
    verbs:
      - "*"
    

    Available at https://github.com/mongodb/mongodb-enterprise-kubernetes/blob/b4c0a9b167f21114dc276cb163a1b207ae2f9359/helm_chart/templates/operator-roles.yaml#L90

    This doesn't doesn't work well with privilege escalation because it won't work for service accounts that individually mention the allowed verbs.
    For example, my service account has permissions for everything (create, delete, deletecollection, get, list, patch, update, watch), but it fails with (...) is attempting to grant RBAC permissions not currently held because they are not equal to "*".

    The proposed change is…

    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 →
  8. 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.

    35 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

    7 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Andrey responded

    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.

  9. 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 →
  10. 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. 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 →
  12. Automatic labeling of pods by replicaset role (primary/secondary)

    Hi, I think it would be great if the Operator could watch and automatically mark individual pods of statefulset with some label indicating whether the node is primary or secondary to be able to route service just to the primary instance (or load balance secondary instances for read-only access on one IP).

    Currently I use a script that periodically checks roles and adds label "mongodb-replicaset-role": "primary" or "secondary" and a service that uses this as a selector.
    EDIT: (I'm thinking about writing own operator for this instead of script; maybe it's the best way?)

    Motivation: Linode (and possibly others') kubernetes…

    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. Migrating existing deployments to MongoDB Kubernetes Operator

    Hello,
    Is there a way to migrate existing non-kubernetes MongoDB clusters to 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base