Opsmanager with mongodb community replicaset

Ops and Admin
, ,
1

Ops manager with Community replica set

I’m currently working on connecting a MongoDB Community Edition replica set to Ops Manager, both residing within the same Kubernetes cluster. While I’m familiar with the process for an enterprise replica set, I’m specifically looking for guidance on achieving this for a community replica set deployment.

Could someone kindly assist me in locating relevant resources or documentation to navigate this particular configuration?

3

Hi @Tanmay_Bhandge and welcome to MongoDB community forums!!

Ops Manager can manage both community and enterprise versions of MongoDB.
However, there is no specific restrictions on the number of community version deployments you can initiate, while there might be resource limitations. For more details you can also reach out to MongoDB Customer Support.

The steps to deploy remains the same for both the community and the enterprise version with some slight modification mentioned for the enterprise version.
Can you follow the steps mentioned in the official MongoDB documentation to Deploy a Replica Set in Ops Manager and let us know the issues that you are facing.

Regards
Aasawari

4

Hi @Aasawari

Thank you for your response.

I am currently in the process of setting up a MongoDB Community Edition ReplicaSet and aiming to integrate it with OpsManager. While I am familiar with the configuration process for the Enterprise edition, I am encountering challenges with the Community edition.

To achieve this, I have been utilizing a specific YAML configuration file. However, during the integration process with OpsManager using the MongoDB Community Operator, I encountered an error. It appears that specific fields, particularly related to opsManager are not recognized or perhaps not supported by the Community Operator.

Given this situation, I am reaching out for guidance or suggestions on how to successfully integrate the MongoDB Community Edition ReplicaSet with OpsManager. Is there a modified approach or an alternative configuration to facilitate this integration?

Error

Error from server (BadRequest): error when creating "community.yaml": MongoDBCommunity in version "v1" cannot be handled as a MongoDBCommunity: strict decoding error: unknown field "spec.opsManager"

---
apiVersion: mongodbcommunity.mongodb.com/v1
kind: MongoDBCommunity
metadata:
  name: example-mongodb
spec:
  members: 3
  type: ReplicaSet
  version: "6.0.5"
  security:
    authentication:
      modes: ["SCRAM"]
  users:
    - name: my-user
      db: admin
      passwordSecretRef: 
        name: my-user-password
      roles:
        - name: clusterAdmin
          db: admin
        - name: userAdminAnyDatabase
          db: admin
      scramCredentialsSecretName: my-scram
  additionalMongodConfig:
    storage.wiredTiger.engineConfig.journalCompressor: zlib
    net:
      port: 40333
---
apiVersion: v1
kind: Secret
metadata:
  name: my-user-password
type: Opaque
stringData:
  password: <your-password-here>

I know in the Enterprise edition we can use the below, but what about the community version?

opsManager:
    configMapRef:
         name: my-project