Edit a Database Resource

The MongoDB Enterprise Kubernetes Operator is deprecated. There will be no future releases. Each version will reach end of life according to the support policy. All of its features are available in the MongoDB Controllers for Kubernetes Operator. Please migrate to the Controllers for Kubernetes Operator for continued support.

You can modify a deployment's configuration and topology, including its MongoDB versions, storage engines, and numbers of hosts or shards. You can make modifications at all levels of a deployment's topology from a top-level sharded cluster or replica set to lower levels, such as a replica set within a sharded cluster, or an individual process within a replica set. You can also modify standalone processes.

Considerations

You can't change individual members of a replica set or sharded cluster. You can change only the whole set or cluster.
If a setting isn't available for a MongoDB resource, you can make changes using only the Ops Manager or Cloud Manager application.
- MongoDB custom resources do not support all mongod command line options. If you use an unsupported option in your object specification file, the backing MongoDB Agent overrides the unsupported options. For a complete list of options supported by MongoDB custom resources, see MongoDB Database Resource Specification.
You can configure certain settings using only the Kubernetes Operator. To review the list of settings, see MongoDB Kubernetes Operator Exclusive Settings.

Prerequisites

Before you update a MongoDB object, complete the following procedures:

Procedure

Edit the Kubernetes resource specification file.

Modify or add settings as needed.

Save your specification file.

Apply the file.

kubectl apply -f <standalone-conf>.yaml

Back

Use with Prometheus

Upgrade MongoDB