Skip to content

Ops Tools

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

49 results found

  1. Support Service Binding Specification for Kubernetes

    Service Binding Specification for Kubernetes standardizes exposing backing service secrets to applications. The spec is available here: https://github.com/servicebinding/spec

    This blog post would be helpful: https://muthukadan.net/kubernetes/binding/support-service-binding-specification-for-kubernetes/

    1 vote
    How important is this to you?
  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
    How important is this to you?
  3. 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
    How important is this to you?
  4. 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
    How important is this to you?
  5. 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
    How important is this to you?
  6. 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
    How important is this to you?
  7. 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
    How important is this to you?
  8. 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
    How important is this to you?
  9. cert-manager & external-dns integration

    Since the kube CA integration is deprecated, the operator should have an option to integrate with cert-manager and external-dns for automatic tls and dns records.

    1 vote
    How important is this to you?
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base