JOSE

← MongoDB Feedback Engine

My feedback

7 results found

  1. Add options to the connection string through the MongoDBUser

    1 vote
    1 comment  ·  Ops Tools » Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    JOSE commented  · 

    We are trying to mimic what you can do in ATLAS:
    https://www.mongodb.com/blog/post/introducing-ability-independently-scale-atlas-analytics-node-tiers
    A standard replica set contains a primary node for reads and writes and two secondary nodes that are read only. Analytics nodes provide an additional read-only node that is dedicated to analytical reads.

    We were able to add a new node to the replica set, have it tagged and with no votes and lower priority, even with potenttialy a different quality in its persistent volumes, so would lilke to have a connection string customized to include the readPreferenceTags.

    We filed a support case, but this is not currently supported in the Operator/MongoDBUser.

    JOSE shared this idea  · 

  2. Allow MongoDBUser CRD to interact with a MongoDB resource in a seperate namespace

    2 votes
    0 comments  ·  Ops Tools » Ops Manager  ·  Admin →
    How important is this to you?
    JOSE supported this idea  · 

  3. Add ability to create user credentials in different namespace then mongo cluster

    2 votes
    0 comments  ·  Ops Tools » Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    JOSE supported this idea  · 

  4. Ops Manager and Backup infrastracture Disaster Recovery support with K8s Operator

    4 votes
    0 comments  ·  Ops Tools » Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    under review  ·  AdminDan (Admin, MongoDB) responded

    There is no current supported mechanism for backing up Ops Manager in a way that guarantees the data. As Ops Manager is itself a backup tool, it's challenging to maintain the integrity of the data in DR scenarios.


    For this reason we recommend multi-site high availability for OM and AppDB. This is already possible when running OM on hardware of in VMs, but not currently supported in Kubernetes (unless a Kubernetes cluster is spanning sites).


    Later this year (2023) we hope to support OM deployments across multiple Kubernetes clusters - as we already support (in beta) for Replica Sets (full release in April 2023 with Sharded cluster support in May/June 2023). Doing so will reduce the criticality of a OM/AppDB backup solution within Kubernetes.

    JOSE supported this idea  · 

  5. Allow the Kubernetes Operator to delete a project

    10 votes
    0 comments  ·  Ops Tools » Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    planned  ·  AdminDan (Admin, MongoDB) responded

    While deletion of a deployment is possible via Kubernetes, deleting a MongoDB resource doesn’t remove it from the Ops Manager UI. You must remove the resource from Ops Manager manually. To learn more, see Remove a Process from Monitoring.


    Deleting a MongoDB resource for which you enabled backup doesn’t delete the resource’s snapshots. You must delete snapshots in Ops Manager.


    Find out more.


    Work is planned to remove Ops Manager as a prerequisite (though it's use will still be optional and supported) and as part of that we hope to address this deletion aspect.

    JOSE supported this idea  · 

  6. OpsManager Application DataBase Backup and Restore

    45 votes
    4 comments  ·  Ops Tools » Ops Manager  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    JOSE commented  · 

    Even if you have an HA environment, it may be needed to do a full restore sometimes, even if this means some downtime of the OpsManager service for some time.

    JOSE supported this idea  · 

  7. Add ability to configure Pod Distruption Budget for STS

    5 votes
    2 comments  ·  Ops Tools » Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    JOSE supported this idea  · 
    An error occurred while saving the comment
    JOSE commented  · 

    100% agree, This should be a task executed automatically by the operator for every new cluster/replicaset. Or at least to have the option to configure it so it is created automatically or not.
    PDBs help on the day 2 operation of a sts in Kubernetes, should be a standard setup.

Feedback and Knowledge Base

(thinking…)