Joel
My feedback
9 results found
-
44 votesJoel
supported this idea
·
-
2 votesJoel
supported this idea
·
-
9 votesJoel
supported this idea
·
-
42 votesJoel
supported this idea
·
-
4 votes
An error occurred while saving the comment Joel
supported this idea
·
-
9 votes
We have an example of a HELM chart that can deploy all resources.
We will be working on adding more refined charts
https://github.com/mongodb/mongodb-enterprise-kubernetes/tree/master/helm_chartAn error occurred while saving the comment Joel
commented
Hi Andrey,
The HELM chart you are referring to is about the deployment of the Operator.
This suggestion is about a HELM chart for the resources needed to deploy a MongoDB instance. Meaning MongoDB CR, MongoDBUser CR(s) and secret(s) for the User.
Joel
shared this idea
·
-
5 votesJoel
supported this idea
·
-
18 votes
An error occurred while saving the comment Joel
commented
Totally agree. I would describe it as follows:
The OpsManager cannot be fully configured via the MongoDBOpsManager resource. There is interaction with the OpsManager API needed for:
- Initial settings wizard (mailserver, email addresses etc.)
- Backup integration
- Creation of a Organization, API keys and IP whitelisting in order to be able to create MongoDB instances for the S3 metadata storage and oplog store
- After that Create a Secret and ConfigMap with the data returned from OpsManagerProvide a k8s native way to Configure the OpsManager without any interaction towards the OpsManager API
Option 1: Provide a way to add this configuration directly in the MongoDBOpsManager resource
Option 2: Provide a way to Configure the OpsManager settings via ConfigMap
An error occurred while saving the comment Joel
commented
When deploying a MongoDB resource to a newly installed Operator and OpsManager the user has to
Create an Organization, API keys and IP whitelisting in OpsManager
Create a Secret and ConfigMap with the data returned from OpsManager
Specify this Configmap as "configMapRef" in the MongoDB resource.Please provide a k8s native way to deploy a MongoDB instance without any interaction towards the OpsManager API. The MongoDB Operator should create the Organization, API keys and IP whitelisting in OpsManager and create the secret and configmap.
Option 1: Create a CRD "MongoDBOpsManagerOrganization" that has a reference to a secret (containing the private key) and an IP whitelist as parameter. The MongoDB resource then references this MongoDBOpsManagerOrganization
Option 2: The MongoDB Operator automatically creates an Organization per Namespace containing MongoDB resources. The user does not need to create any Organization, API keys, IP whitelisting, Secret and ConfigMaps.
Joel
supported this idea
·
-
6 votesJoel
shared this idea
·
Permissions should include allowing mongodump --oplog the entire ReplicaSet (e.g. admin DB) and execute db.fsyncLock() in order to perform filesystem level backups.