At any place on this page that says Ops Manager, you can substitute Cloud Manager.
You can use the Kubernetes Operator to deploy MongoDB resources with Cloud Manager and with Ops Manager version 5.0.x or later.
You can use the Atlas Operator to deploy MongoDB resources to Atlas.
Kubernetes Operator doesn't support arbiter nodes.
A replica set is a group of MongoDB deployments that maintain the same data set. Replica sets provide redundancy and high availability and are the basis for all production deployments.
To learn more about replica sets, see the Replication Introduction in the MongoDB manual.
Use this procedure to deploy a new replica set that Ops Manager manages. After deployment, use Ops Manager to manage the replica set, including such operations as adding, removing, and reconfiguring members.
When you deploy your replica set via the Kubernetes Operator, you must choose whether to encrypt connections using TLS certificates.
The following procedure for TLS-Encrypted connections:
Establishes TLS-encrypted connections between MongoDB hosts in the replica set.
Establishes TLS-encrypted connections between client applications and MongoDB deployments.
Requires valid certificates for TLS encryption.
The following procedure for Non-Encrypted Connections:
Doesn't encrypt connections between MongoDB hosts in the replica set.
Doesn't encrypt connections between client applications and MongoDB deployments.
Has fewer setup requirements than a deployment with TLS-encrypted connections.
You can't secure a Standalone Instance of MongoDB in a Kubernetes cluster.
To set up TLS encryption for a sharded cluster, see Deploy a Sharded Cluster.
Select the appropriate tab based on whether you want to encrypt your replica set connections with TLS.