Ops Tools
38 results found
-
Release K8S Ops Manager image when Ops Manager release is out
Currently there is a time lag between the Ops Manager version releases and the availability of K8S images to be used with the MongoDB Kubernetes Operator.
It would be nice if they are released at the same time.
2 votesWe now update Ops Manager images on the same day with Ops manager releases.
-
Prevent users from importing a replica set or shard with the same name as other pre-existing replica sets/shards
When a user imports a cluster into a project with the same name, it causes issues like breaking backups of pre-existing clusters.
Checking the replica set name against the names of other replica set names will prevent having to terminate backups and remove and re-import clusters, starting over.
2 votes -
Allow to configure options for automation agent logs
Currently there is no way in Kubernetes operator to configure how long automation/backup/monitoring agent logs should be stored. they can easily occupy all space in pod.
2 votes -
Support Helm Chart for operator
Provide Helm charts for MongoDB Enterprise operator
2 votesWe have support for deploying the Operator with Helm.
We do not currently cover deploying and managing the custom resources for deployments etc using Helm. Please raise a separate feedback item if this is of interest.
-
OpsManager in Kubernetes Deployment
Deploy MongoDB Ops Manager in Kubernetes with Operator that will allow MongoDB Clusters to be run and managed from Kubernetes platform entirely
2 votes -
Add new SCRAM Authz to MongoDBUser CR
Support SCRAM authentication for MongoDB Users
2 votes -
Custom Pod Annotations
This is regarding usage of service mesh / policy agent automations for stateful sets.
1 voteThis is already possible actually! Though it's definitely an area where we need to improve our docs.
In any valid working MongoDBCommunity deployment you'd need to specify:
spec:
statefulSet:
spec:
template:
metadata:
annotations:
example.com/annotation-1: "value-1"
example.com/annotation-2: "value-2"And obviously alter the annotations according to your needs!
-
Allow creation of Custom Roles in AtlasDeployment
I'm missing a feature to create custom roles from deployment level for Atlas operator (as already possible in community operator: https://github.com/mongodb/mongodb-kubernetes-operator/blob/b232901f5c6e4f9c1ab04bc9725458ca70a19930/config/crd/bases/mongodbcommunity.mongodb.com_mongodbcommunity.yaml#L173-L258)
1 vote -
k8s operator - Support different different size shard configuration
We would like to implement the Hot-cold shard strategy to move the cold data to a shard which has more disk usage and less compute power and not frequently used and Hot data in a shard with more compute power. This strategy is described here: https://docs.mongodb.com/manual/tutorial/sharding-tiered-hardware-for-varying-slas/
Currently the enterprise operator does not support different size shards, this request is to allow operator to create different size shards.
1 voteWe have recently released the ability to support different sized shards and that enables the scenario described in this idea.
This is supported in 1.19.1 of the Operator, the release notes can be found here and the relevant section is as follows:
- Allows you to configure podSpec per shard in a MongoDB sharded cluster by specifying an array of podSpecs under the spec.shardSpecificPodSpec setting for each shard.
-
Kubernetes Operator - Enable S3 Oplog store
Currently, only Replica Sets are the only to deploy an Oplog Store with the Kubernetes Operator.
This causes issues related to sizing for Ops Manager deployments managing a big number of projects.
Enabling S3 Oplog Store would help a lot.1 voteWe do now support this, but it's not yet covered in our docs (a ticket is open but not yet completed.)
We do however have a public example of setting this up, which should enable you to use it.
-
Automatic labeling of pods by replicaset role (primary/secondary)
Hi, I think it would be great if the Operator could watch and automatically mark individual pods of statefulset with some label indicating whether the node is primary or secondary to be able to route service just to the primary instance (or load balance secondary instances for read-only access on one IP).
Currently I use a script that periodically checks roles and adds label "mongodb-replicaset-role": "primary" or "secondary" and a service that uses this as a selector.
EDIT: (I'm thinking about writing own operator for this instead of script; maybe it's the best way?)Motivation: Linode (and possibly others') kubernetes…
1 voteSince this was raised we've added support for load balancer (rather than just nodeport). Since this would be one load balancer for the entire replica set, this may reduce the cost?
https://www.mongodb.com/docs/kubernetes-operator/master/tutorial/connect-from-outside-k8s/
Please let us know via a comment if this doesn't solve the need.
-
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 voteIt is now possible to specify a particular tag, rather than latest.
-
1 vote
This is fully supported for all containers deployable via the Enterprise Operator.
This is covered in the relevant parts of the documentation: https://www.mongodb.com/docs/kubernetes-operator/master/
-
OpsManager Pod should not have credentials in environment variables but store and retrieve from a k8s secret
OpsManager database password is exposed as environment variable.
OMPROPmongo_mongoUri holds credentials of the OpsManager Database.
OpsManager Pod should not have credentials in environment variables but store and retrieve from a k8s secret.
1 voteWe moved all passwords to a secret
-
Allow to configure MongoDB pods service user
Currently in MongoDB Kubernetes Operator 1.4.2 the pods are run under a specific service user named "mongodb-enterprise-database-pods".
It would be nice to be able to specify a custom service user name to be able to comply to specific enterprise user definition rules.
1 vote -
Allow custom Annotations on MongoDB CR
Allow custom Annotations on MongoDB CR so it would be easier to label multiple clusters
1 vote -
Release operator images based on UBI
Support UBI as a base image for OpenShift deployemnts
1 vote -
Add Taints and Tolerations to K8S Operator pod spec
Add capability to add Taints and Tolerations to K8S Operator pod spec for different types of pods
0 votesOperator can not accept full PodSpecTemplate. Taints could be configured using normal K8S functions
- Don't see your idea?