Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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

    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. Support Helm Chart for operator

    Provide Helm charts for MongoDB Enterprise 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

    planned  ·  1 comment  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. 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 →
  5. 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. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. Have the MongoDB operator support k8s route sharing for connecting to replicas to simplify network and not use nodeport

    It's still very new and only kube-router is the only "free" one that supports it. But this is great simplify the network configurations to connect to replicas and shards.

    Route Sharing is currently supported on Red Hat OpenShift 4.4+

    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. 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 →
  19. operator should watch * namespace by default

    So that way multiple projects can leverage the single operator to provision mongodb. https://github.com/mongodb/mongodb-enterprise-kubernetes/issues/164

    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 should watch * namespace by default

    So that way multiple projects can leverage the single operator to provision mongodb. https://github.com/mongodb/mongodb-enterprise-kubernetes/issues/164

    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 →
  • Don't see your idea?

Feedback and Knowledge Base