Upgrade Ops Manager and Backing Database Versions

On this page

Prerequisites

Procedure
In your , the settings as shown in the following example:
Reapply the configuration to Kubernetes.

This version of the operator is no longer officially supported. View the current documentation to learn how to upgrade your version of MongoDB Enterprise Kubernetes Operator.

Update the major and minor versions of your Ops Manager instance and backing databases in the Ops Manager Resource Specification that the Kubernetes Operator uses to manage your deployment.

Prerequisites

Warning

To maintain existing settings and availability, back up the following in your current Ops Manager instance:

Your conf-mms.properties to a secure location. The conf-mms.properties stores settings for the Ops Manager instance.
Your gen.key files to a secure location. The gen.key provides details to encrypt and decrypt Ops Manager's backing databases and user credentials. Ops Manager might delete these files as part of the upgrade process.
Your application database. If the upgrade fails, you need a current backup to restore your Ops Manager instance.

Upgrade Ops Manager by following the considerations, prerequisites, and procedure in Upgrade Ops Manager.
Reference Use a Compatible MongoDB Version to ensure your backing databases use a MongoDB version that is compatible with the new Ops Manager version.
If you need to upgrade your backing databases to a compatible MongoDB version, see Upgrade MongoDB Version and FCV.

Procedure

To update Ops Manager from 5.0 to 6.0 and the application database to MongoDB 4.4.18-ent, complete the following steps:

In your Ops Manager Resource Specification, the settings as shown in the following example:

Set spec.version to the new Ops Manager version.
If you upgraded your application database, set spec.applicationDatabase.version to the compatible MongoDB version.

(Optional) If you might need to downgrade, set spec.featureCompatibilityVersion.

1 apiVersion: mongodb.com/v1
2 kind: MongoDBOpsManager
3 metadata:
4  name: om
5 spec:
6  replicas: 1
7  version: "6.0.0"
8  adminCredentials: ops-manager-admin
9  configuration:
10   mms.fromEmailAddr: admin@example.com
11   mms.security.allowCORS: "false"
12  backup:
13   enabled: true
14   encryption:
15     kmip:
16       server:
17         url: kmip.corp.mongodb.com:5696
18         ca: mongodb-kmip-certificate-authority-pem
19   headDB:
20    storage: "30Gi"
21    labelSelector:
22     matchLabels:
23      app: my-app
24   opLogStores:
25    - name: oplog1
26                        # Sets labels for the oplog store.
27      assignmentLabels: ["test1", "test2"]
28      mongodbResourceRef:
29       name: my-oplog-db
30      mongodbUserRef:
31       name: my-oplog-user
32   s3Stores:
33    - name: s3store1
34                        # Sets labels for the S3 store.
35      assignmentLabels: ["test1", "test2"]
36                        
37      mongodbResourceRef:
38       name: my-s3-metadata-db
39      mongodbUserRef:
40       name: my-s3-store-user
41      s3SecretRef:
42        name: my-s3-credentials
43      pathStyleAccessEnabled: true
44      s3BucketEndpoint: s3.region.amazonaws.com
45      s3BucketName: my-bucket
46 
47  applicationDatabase:
48    passwordSecretKeyRef:
49     name: om-db-user-secret
50     key: password
51    members: 3
52    version: "4.4.5-ubi8"

Reapply the configuration to Kubernetes.

kubectl apply -f <om-resource-specification>.yaml

Kubernetes automatically reconfigures your deployment with the new specifications. You can see these changes reflected in your Ops Manager or Cloud Manager application.

Back

Configure an

Configure Queryable Backups for

1	apiVersion: mongodb.com/v1
2	kind: MongoDBOpsManager
3	metadata:
4	name: om
5	spec:
6	replicas: 1
7	version: "6.0.0"
8	adminCredentials: ops-manager-admin
9	configuration:
10	mms.fromEmailAddr: admin@example.com
11	mms.security.allowCORS: "false"
12	backup:
13	enabled: true
14	encryption:
15	kmip:
16	server:
17	url: kmip.corp.mongodb.com:5696
18	ca: mongodb-kmip-certificate-authority-pem
19	headDB:
20	storage: "30Gi"
21	labelSelector:
22	matchLabels:
23	app: my-app
24	opLogStores:
25	- name: oplog1
26	# Sets labels for the oplog store.
27	assignmentLabels: ["test1", "test2"]
28	mongodbResourceRef:
29	name: my-oplog-db
30	mongodbUserRef:
31	name: my-oplog-user
32	s3Stores:
33	- name: s3store1
34	# Sets labels for the S3 store.
35	assignmentLabels: ["test1", "test2"]
36
37	mongodbResourceRef:
38	name: my-s3-metadata-db
39	mongodbUserRef:
40	name: my-s3-store-user
41	s3SecretRef:
42	name: my-s3-credentials
43	pathStyleAccessEnabled: true
44	s3BucketEndpoint: s3.region.amazonaws.com
45	s3BucketName: my-bucket
46
47	applicationDatabase:
48	passwordSecretKeyRef:
49	name: om-db-user-secret
50	key: password
51	members: 3
52	version: "4.4.5-ubi8"