Skip to content

Ops Tools

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

47 results found

  1. Authentication mode MONGODB-OIDC

    Support for authentication: MONGODB-OIDC

    security:
    authentication:
    enabled: true
    modes:
    - "MONGODB-OIDC"

    currently we get the following error wir kuberntes operator 1.26.0, OpsManager 7.0.7 and RS 7.0.11:
    Unsupported value: "MONGODB-OIDC"

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We're considering this for inclusion into Q4 (by end of January) - but we're currently reviewing priorities for a number of projects competing for attention.

  2. Operator crashes when it doesn't have permissions to watch a namespace

    If one of many namespaces does not set the permissions for the operator to watch the namespace, it throws exceptions and goes to crashLoopBackOff state.
    This is clearly a bug. One misconfigured namespace should never be able to take the operator down with it.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This is expected behavior and common among operators; it can't function and do what's needed if it lacks the permissions needed.


    I know we have an open support case around this to try and understand more about your use case, and we're hoping that we'll be able to offer some guidance to avoid this problem and still achieve what you need. It may even be a new use case that we look to support.

  3. Allow configuring external applicationDatabase running on MongoDB Atlas

    Allow configuring external applicationDatabase running outside of Kubernetes in the opsManager configuration.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow service spec changes via MongoDBCommunity CR

    I aim to include extra sidecar containers, such as a metrics sidecar, allowing me to deploy an external metrics exporter alongside that would be scraped via service. I intend to configure annotations on the service for Prometheus automatic discovery, enabling the scraping of metrics and exposing the exporter container at the service level, similar to the one exposed when prometheus integration is enabled.

    Updating the service spec is not currently possible, and as result, a lot of manual steps are required, like creating a custom service for each cluster, which points to the sidecar container with the required annotations in…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add support to convert a replica set to a sharded cluster in Kubernetes

    Currently it is not possible to use Ops Manager UI or Kubernetes Operator to convert Replica Set to Sharded cluster. Error : changed not allowed.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Planned - we have a requirement to have this completed in time for MongoDB 9.0. But no timeline (yet) for delivering this within that timeframe. 

  6. Add comprehensive configuration options for persistent volumes

    From a project point of view, we need additional configuration options for persistent volumes. For instance, as far as we know, each MongoDB Deployment that uses a persistent volume is configured with Access Mode ReadWriteOnce per default. We need to customise this option for optimal usage. For configuration options would be a plus.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Improve Enterprise Kubernetes Operator PVC expansion

    The enterprise operator should be capable of performing all the steps necessary to increase the PVC after the end-user has adjusted the storage values within the MongoDB custom resource.

    Reference:
    https://www.mongodb.com/docs/kubernetes-operator/stable/tutorial/resize-pv-storage/

    Why is the Operator incapable of doing the steps starting from step 3 by itself if I simply do step 5?

    So what we think should be the case:

    We update the database resource with a new storage value.

    Then should perform the following steps:

    • Patch each persistence volume which can be found in the sts / pod spec.
    • Remove the sts with --orphan because the name should be…
    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Add options to the connection string through the MongoDBUser

    We would like to add options to the connection string that is generated by the operator when creating a new MongoDBUser.
    The idea is to include these options in the MongoDBUser CRD so the operator can then add them to the connectionString stored in the generated secret.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add a variable for set the RS name

    Add own variable to set the RS name so that the deployment name can be used to name the pod

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. monitoring opt

    Allow to configure startupOptions for monitoring/backup agent logs in yaml for deployments. Similar as we have for AppDB - spec.applicationDatabase.monitoringAgent.startupOptions

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Enable external-dns integration via per-service annotations on each generated service

    Currently the MongoDB Kubernetes Operator allows specification of annotations on services created by the operator, but only annotations with the same value across all services. The external-dns operator can create DNS names based on annotations on services. In order to support external-dns integration the MongoDB Kubernetes Operator would need to allow one to specify specific annotations for each generated service.

    Current spec for external access services:
    externalAccess:
    externalService:
    annotations:
    # Same annotations will be applied on all services

    You could consider a placeholder/substitution scheme like:
    externalAccess:
    externalService:
    annotations:
    external-dns.alpha.kubernetes.io/hostname: mydb-db-<instance number>.mydns.com

    Or some other way of assigning a per-service annotation…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. There have been at least a few issues on Kubernetes Community Operator related to PVC expansion, yet this is not documented anywhere.

    There have been at least a few issues on Kubernetes Community Operator related to PVC expansion, yet this is not documented anywhere.

    Looking at closed issues, one may get an idea that this operation is impossible, but with the latest CSI it should be - it requires some handcrafting. On the other side Enterprise operator has this covered here - https://www.mongodb.com/docs/kubernetes-operator/stable/tutorial/resize-pv-storage/. I suggest writing similar how-to for the Community operator.
    My currently tested workflow for volume expansion is similar to this explained on the page above, but as for my knowledge Community operator doesn't allow this operation - as…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow configuration of alerts (and setting customer alerts) via enterprise operator

    It would be nice to be able to configure an environments alerts directly from the Operator which will be deploying that environment.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Allow the services port name prefix customization in Enterprise Kubernetes Operator to support Istio Sidecar requisites

    Istio Sidecar requires services port name prefix with a protocol name, but the services port names created by the Enterprise Kubernetes Operator are not customizable (e.g.)

    • operator-webhook
    • ops-manager-backup-daemon-svc
    • ops-manager-db-svc
    • ops-manager-svc

    It may be possible to allow the customization of these names?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Migration Guide for OpsManager to enterprise-operator

    It would be great to have a migration guide or documentation to help with migrating an existing OpsManager installation to the kubernetes enterprise-operator based installation.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Rotate mongo logs

    When cluster is deployed, each mongo server start to generate a logfile "/var/log/mongodb-mms-automation/mongodb.log", we got an outage because it gets the disk full.
    It will be useful if we can specify a value to rotate and purge the log.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Timeline on Server internal authentication via Keyfile

    Hi Operator team,

    The K8s operator community edition README mentions the feature Server internal authentication via keyfile is in progress. My team is hoping to use this feature on our current project and wanted to ask what the timeline is for this. Is it likely to be included in the next release, and if so when is that release? Thanks!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. arm64 support for Kubernetes Operator

    Arm64 processors are getting more and more popular. Would be really nice to be able to run MongoDB Kubernetes Operator on a Raspberry Pi cluster.

    Otherwise, meanwhile would be nice to get documentation updated on how to produce arm64 images to still make it possible without having full CI infrastructure support.

    16 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add ability to create user credentials in different namespace then mongo cluster

    As the title states. I am creating my mongo cluster in a different namespace then my application, however because k8s does not allow sharing secrets between namespaces it is impossible to access the credentials.

    I suggest adding a namespace field inside of the users definition to allow the creation of the secret in another namespace.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base