Ops Tools
-
Pin versions for all images in values file
currently for release 1.9.0, the helm chart has no way to explicitly use a specific version of the following images:
- mongodb-enterprise-ops-manager
- mongodb-enterprise-appdbThis is not ideal and hard to scale in the enterprise. Request the ability to pin versions to all images from values file.
1 vote -
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.
1 vote -
Ops Manager LDAP Auth using kubernetes manifest
Currently, there is no way to enable LDAP Auth for the Ops Manager Users on my kubernetes Ops Manager pods using manifests.
This essentially means that one would not be able to use LDAP and ci/cd simultaneously with Ops Manager with the enterprise kubernetes operator.
Mongodb enterprise support has confirmed that in the event of disaster recovery or a deployment of a new cluster, manual steps must be done to enable LDAP during a ci/cd deployment.
It should not be expected to sign in and manually do anything in a web gui in an enterprise solution. It is simply not…
1 vote -
Pin image tags in Enterprise Kubernetes Operator values file
Should be able to pin tags for images like
mongodb-enterprise-appdbin https://github.com/mongodb/mongodb-enterprise-kubernetes/blob/master/helm_chart/values.yamlCurrently, we are forced to use the latest tag, which has caused issues and broke disaster recovery for our project.
If we would have been able to use an older tag of the image, we could have recovered fast. since we were forced to use the latest tag, it took several days to recover. This does not seem acceptable for an enterprise software.
1 vote -
sharding
Should provide sharding feature in community Operator.
1 vote -
Have the MongoDB operator support k8s route sharing for connecting to replicas to simplify network and not use nodeport
It's still very new and only kube-router is the only "free" one that supports it. But this is great simplify the network configurations to connect to replicas and shards.
Route Sharing is currently supported on Red Hat OpenShift 4.4+
1 vote -
1 vote
-
operator should watch * namespace by default
So that way multiple projects can leverage the single operator to provision mongodb. https://github.com/mongodb/mongodb-enterprise-kubernetes/issues/164
1 vote -
operator should watch * namespace by default
So that way multiple projects can leverage the single operator to provision mongodb. https://github.com/mongodb/mongodb-enterprise-kubernetes/issues/164
1 vote -
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 -
Allow customizing mongod port in kubernetes
The additionalMongodConfig feature was a great addition to the Operator.
Setting the spec.additionalMongodConfig.net.port to a value other than the default 27017 is not working as expected. The default port is still used despite the custom port value appearing in the MongoDB resource description/manifest. A common security compliance checklist often includes running services on non-default ports.
Please consider allowing the net.port to be set to a custom value; this may have implications with the services that are automatically created in the cluster.
1 vote
- Don't see your idea?