The first step in deploying a MongoDB database in Kubernetes is to install the Kubernetes Operator. The Kubernetes Operator acts as the control plane that manages the full operational lifecycle of your database, but it does not create the database automatically upon installation.
After you install the Kubernetes Operator and get it running, you must then deploy:
The MongoDB custom resource, which specifies the desired state of your database cluster, such as its version, replica set size, and storage requirements.
A Cloud Manager or Ops Manager instance to handle automation, monitoring, and backup orchestration.
Networking configurations to ensure communication between the Kubernetes Operator, Cloud Manager or Ops Manager agents, and your applications.
For more complex scenarios, such as multi-cluster deployments, use a reference architecture (a template). To learn more, see How to Use Reference Architectures.
Installation and Configuration Guides
- Plan your MongoDB Controllers for Kubernetes Operator Installation
- Review Kubernetes Operator deployment architecture, scopes, considerations, and prerequisites.
- Install the MongoDB Controllers for Kubernetes Operator
- Install the MongoDB Controllers for Kubernetes Operator.
- Migrate to MongoDB Controllers for Kubernetes Operator
- Migrate from previous MongoDB Kubernetes deployment tools to Kubernetes Operator.
- Verify the Integrity of the MongoDB Controllers for Kubernetes Operator Packages
- Verify the package is valid and unaltered before you install Kubernetes Operator.
- Upgrade the Kubernetes Operator from Prior Versions
- Upgrade from earlier versions of Kubernetes Operator.