Ops Tools
42 results found
-
allow to configure startupOptions for monitoring/backup agent logs
Allow to configure startupOptions for monitoring/backup agent logs in yaml for deployments. Similar as we have for AppDB - spec.applicationDatabase.monitoringAgent.startupOptions
3 votes -
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
1 vote -
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 servicesYou could consider a placeholder/substitution scheme like:
externalAccess:
externalService:
annotations:
external-dns.alpha.kubernetes.io/hostname: mydb-db-<instance number>.mydns.comOr some other way of assigning a per-service annotation…
1 vote -
2 votes
-
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 votePlanned - no fixed date but likely complete within Q2.
-
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?
2 votes -
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.
14 votesARM support is now in progress for the Community Operator (https://github.com/mongodb/mongodb-kubernetes-operator) and will be released in the next few weeks.
ARM support for the Enterprise Operator is TBD but is in the roadmap, likely for 2024.
-
Reconciliation resources flag improvement
atlas-reconciliation-policy=skip flag provide ability do not sync k8s object status with atlas. But in case when we need to make reference on objects in Atlas (Aka project) and do not create or modify this resource - this flag not very useful nothing. In this case i would be good if
- or operator sync object from API to k8s resources ( grub id by name so k8s resource will be valid )
- or at least provide opportunity to set id ( for new resources with atlas-reconciliation-policy=skip set by default )
Aka:- Follow the pattern of reading data from the…
2 votes -
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.
1 vote -
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 -
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 -
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 -
Timeline on Server internal authentication via Keyfile
Hi Operator team,
The K8s operator community edition README mentions the feature
Server internal authentication via keyfileis 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 -
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 MongoDB statefulset and service selector should use a label prefixed with a MongoDB domain.
https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set
4 votesWe're gradually starting to change things to prefix most annotations and labels with mdb.
It's a gradual thing but in progress.
-
MongoDB kubernetes operator - follow recommended kubernetes object labeling -
Hi, i would like to thank you first for this operator, good job 👍 . It works well.
Did you consider using this label convention for objects (statefulset, svc, secrets) https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/?
Currently in my cluster Im trying to follow these recommended labels for objects while Im forwarding kubernetes logs using EFK but cannot store log to elasticsearch because there is object mapping for
kubernetes.labels.appfield as object not a concrete value. Right now there is hard-coded service selector https://github.com/mongodb/mongodb-kubernetes-operator/blob/1aa7093d2cc977bc3b1f5a5fa7e1e902d37768c8/controllers/replica_set_controller.go#L455 which expects pods to be labeled withapp=<serviceName>Example labels following conventions for statefulset:
…apiVersion: apps/v1 kind: StatefulSet metadata: labels:2 votesNo current plans, but under consideration for inclusion on the roadmap in the future.
-
EmptyDir as data-volume and log-volume
spec:
members: 1
type: ReplicaSet
version: "4.4.5"
statefulSet:
spec:
template:
spec:
volumes:
- name: data-volume
emptyDir: {}
- name: log-volume
emptyDir: {}This type of override would be very helpful for automated testing pipelines - pipeline should spin up single mongodb instance, populates data and proceed with application testing. For that, we don't need persistent volumes, we need clear folder on each invocation.
1 vote -
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 voteLow customer demand. Potentially in the future if we hear sufficient demand.
-
Allow the Kubernetes Operator to delete a project
Currently it is not possible to delete a project via kubectl command.
As the Kubernetes Operator allows one to create a project (configmap) and deploy a replica set, we would expect it to also allow the deletion of a project so that we can fully automate the solution.
8 votesWhile 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.
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.
-
Allow disabling Blockstore for assignment through the Ops Manager CRD
By default, when enabling backups and configuring a Blockstore for an Ops Manager custom object, the specified Blockstore will be set as "Assignment enabled" in the UI.
It would be helpful to expose the enable/disable button for the blockstore through the CRD since disabling it through the UI, results in the parameter being reverted every time the operator consolidates. This is useful for the case when more than a single store is configured and as a user you would like to disable the blockstore to make it unavailable for new backup jobs.
3 votes -
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
- Don't see your idea?