Skip to content

Ops Tools

← MongoDB Feedback Engine

How can we improve the Operational Tooling MongoDB provides?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

3 results found

  1. Add CRD for Trigger Functions.

    We would like to create a Scheduled Trigger Function for a federated database instance, and currently the Operator does not support this resouce. Do you have any future plans to support Trigger Functions with the Atlas Kubernetes Operator? Or is there any alternate solution that you would recommend?

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Community Kubernetes Operator  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Add imagePullPolicy to the CRD

    I want to set imagePullPolicy for every container created with the Mongo DB Commnunity Operator.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Community Kubernetes Operator  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Add specific label to Arbiter deployment to distinguish it label-wise

    As per https://github.com/mongodb/mongodb-kubernetes-operator/issues/1442 we would like to request to either and/or:

    a) have the operator add a new label to replica and arbiter statefulset deployments to distinguish them from each other
    b) have the ability to add your own labels to specifically the replica OR the arbiter statefulset deployments

    Having the ability to easily filter arbiter statefulsets from non-arbiter statefulsets would be great. This is useful for example for backup tools that run commands on pods based on a combination of labels, to exclude any arbiters from backup.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Community Kubernetes Operator  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

Ops Tools

Categories

Feedback and Knowledge Base

(thinking…)