> 1.) What is the limiting factor of the Operator? Is it number of Pods, number of Custom Resources (e.g. MongoDB, MongoDBUser) or something else?
> 2.) What does the number of "Clusters" refer to? Does it differ for Standalone, ReplicaSet and ShardedCluster?
> 3.) How many instances of the "Clusters" in 2.) are supported per MongoDB Operator?
Is there any way to add this sort of data to our documentation?
Provide a helm chart that deploys MongoDB, MongoDBUser, secrets and all other resources needed.
The goal is to simplify the deployment of a MongoDB instance and everything that comes with it down to a helm one-liner.4 votes
We have an example of a HELM chart that can deploy all resources.
We will be working on adding more refined charts
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?