- Deploy and Configure MongoDB Database Resources >
- Deploy a MongoDB Database Resource >
- Deploy a Standalone MongoDB Instance
Deploy a Standalone MongoDB Instance¶
On this page
Note
At any place on this page that says Ops Manager, you can substitute Cloud Manager.
Important
- 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.
You can deploy a standalone MongoDB instance for Ops Manager to manage. Use standalone instances for testing and development. Do not use these deployments for production systems as they lack replication and high availability. For all production deployments use replica sets. To learn about replica sets, see Deploy a Replica Set.
Prerequisites¶
To deploy a standalone using an object, you must:
- Have or create an Ops Manager instance or a Cloud Manager organization.
- Have or install the MongoDB Enterprise Kubernetes Operator.
- Create or generate a Kubernetes Operator ConfigMap.
- Create credentials for the Kubernetes Operator or configure a different secret storage tool.
Note
To avoid storing secrets in Kubernetes, you can migrate all secrets to a secret storage tool.
Procedure¶
Configure the settings highlighted in the preceeding step as follows.¶
Key | Type | Description | Example |
---|---|---|---|
metadata.name |
string | Label for this Kubernetes standalone object. Resource names must be 44 characters or less. See also
|
my-project |
spec.version |
string | Version of MongoDB that is installed on this standalone. The format should be Important Ensure that you choose a compatible MongoDB Server version. Compatible versions differ depending on the base image that the MongoDB database resource uses. To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual. |
For best results, use the latest available enterprise MongoDB version that is compatible with your Ops Manager version. |
string | Name of the ConfigMap with the Ops Manager connection
configuration. The
Note This value must exist on the same namespace as the resource you want to create. |
<myproject> |
|
spec.credentials |
string | Name of the secret you created as Ops Manager API authentication credentials for the Kubernetes Operator to communicate with Ops Manager. The Ops Manager Kubernetes Secret object holding the Credentials must exist on the same Namespace as the resource you want to create. Operator manages changes to the Secret The Kubernetes Operator tracks any changes to the Secret and reconciles the state of the MongoDB Kubernetes resource. |
<mycredentials> |
spec.type |
string | Type of MongoDB Kubernetes resource to create. | Standalone |
spec.persistent |
string | Optional. If this value is To change your Persistent Volume Claims configuration, configure the following collections to meet your deployment requirements:
Warning Grant your containers permission to write to your Persistent Volume.
The Kubernetes Operator sets Note If you do not use Persistent Volumes, the Disk Usage and Disk IOPS charts cannot be displayed in either the Processes tab on the Deployment page or in the Metrics page when reviewing the data for this deployment. |
true |
Add any additional accepted settings for a Standalone deployment.¶
You can also add any of the following optional settings to the object specification file for a Standalone deployment:
spec.additionalMongodConfig
spec.exposedExternally
spec.logLevel
spec.featureCompatibilityVersion
spec.podSpec.persistence.single
spec.podSpec.persistence.multiple.data
spec.podSpec.persistence.multiple.journal
spec.podSpec.persistence.multiple.logs
spec.podSpec.podAffinity
spec.podSpec.podTemplate
spec.podSpec.nodeAffinity
Save this file with a .yaml
file extension.¶
Start your Standalone deployment.¶
Invoke the following Kubernetes command to create your standalone:
Track the status of your standalone deployment.¶
To check the status of your MongoDB Kubernetes resource, invoke the following command:
The -w
flag means “watch”. With the “watch” flag set, the output
refreshes immediately when the configuration changes until the status phase
achieves the Running
state.
See Troubleshoot the Kubernetes Operator for information about the resource deployment statuses.
To troubleshoot your sharded cluster, see: