Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Feedback

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 -...
Marco Barbierato over 3 years ago in Kubernetes 0 Submitted

we have an ask to use 4 in snapshotIntervalHours

For the api - https://www.mongodb.com/docs/ops-manager/current/reference/api/backup/update-one-snapshot-schedule-by-cluster-id/ we have an ask to use 4 in snapshotIntervalHours. Right now its not supported. Supported ones are - 6, 8, 12, or 24. P...
Guest about 1 year ago in Backup & Restore 0 Submitted

Kubernetes Operator - Prefix Annotations and Labels

Labels and annotations added to Kubernetes resources by the MongoDB Enterprise Operator should include a prefix designating that it was added by MongoDB. The lack of a prefix suggests the field and values are private to the user. For example, the...
Guest over 4 years ago in Kubernetes 0 Started

In the event of an integrity check job failure, an alert should be shown on Ops manager UI instead of solely relying on email

Integrity Check Jobs failures get emailed to the configured "mms.backup.alertsEmailAddr" address and logged in daemon.log. This information should also be available in Ops Manager UI so that the user can quickly check before trying any restoration.
Guest about 6 years ago in Backup & Restore 0 Submitted

To setup number of backup daemons in ops-manager.yaml

In ops-manager.yaml, can we define the number of the initial backup daemons?
Guest about 6 years ago in Kubernetes 2 Future Consideration

Automatically move HEADS in case of backup daemon problem

In configuration with multiply daemons in case of daemon problem (down) switch to another one automatically with restart backup upon need.
Ilya Shifman about 1 year ago in Backup & Restore 0 Submitted

Use separate tls.crt and tls.key items in a kubernetes secret for certificates instead of a combined item named server.pem for a MondoDB rep

There should be a way to use separate `tls.crt` and `tls.key` items in a kubernetes secret for certificates instead of a combined item named `server.pem`. We request our certs using cert-manager which generates secrets from the cert CRD and will ...
Guest about 5 years ago in Kubernetes 1 Planned

Ops Manager and Backup infrastracture Disaster Recovery support with K8s Operator

We have carried out tests with MongoDB v1.5.5 K8s Operator and Ops Manager 4.2.18 with Backup infrastructure (S3 Snapshots) in an Openshift 3.11 environment (MongoDB Support case attached). In this case, a "Disaster Recovery" simulation has been ...
Guest about 5 years ago in Kubernetes 0 Future Consideration

Operator opsManager.configMapRef as a secret

currently inside the mongodb Operator custom resource `MongoDB`, a configMap stores the orgId. e.g. ``` apiVersion: mongodb.com/v1 kind: MongoDB metadata: name: my-mongodb spec: ... opsManager: configMapRef: name: my-mongodb-ops-manager-diga-...
Guest over 1 year ago in Kubernetes 0 Submitted

Create AppDB user with backup role to allow execution of mongodump

For the purpose of regularly performing backups of the AppDB using mongodump --oplog.
Guest over 5 years ago in Kubernetes 1 Future Consideration