升级 Ops Manager 和后端数据库版本

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.

先决条件

警告

要保持现有设置和可用性，请在当前 Ops Manager 实例中备份以下内容：

将您的conf-mms.properties到安全位置。 conf-mms.properties存储 Ops Manager 实例的设置。
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.

As an extra precaution, you may use mongodump to create a binary export of the Application Database. No officially supported backup method exists for the Application Database. If the upgrade fails, contact MongoDB Support for help fixing the issue with the Ops Manager version.

Upgrade Ops Manager by following the considerations, prerequisites, and procedure in Upgrade Ops Manager.

重要
Don't skip major Ops Manager versions when you upgrade. Upgrade to the latest available patch release of your current major version, then upgrade to the next major version. Repeat this process until you reach your target version. For example, to upgrade from 7.0.x to 8.0, first upgrade to the latest available 7.0 patch release. To find the upgrade path for your current version, see 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.
如果需要将后端数据库升级到兼容的MongoDB版本，请参阅升级MongoDB版本。

步骤

要升级MongoDB Ops Manager和应用程序数据库版本，请完成以下步骤：

在MongoDBMongoDB Ops Manager Ops Manager资源规范中，设置如以下示例所示：

将spec.version设置为新的 Ops Manager 版本。
如果您升级了应用程序数据库，请将spec.applicationDatabase.version设置为兼容的 MongoDB 版本。

重要

请务必选择兼容的 MongoDB Server 版本。

兼容版本因 MongoDB 数据库资源使用的基础图片而异。

警告

如以下示例所示，由于与当前Ops Manager部署关联的应用程序数据库资源以滚动方式升级，因此您必须在开始升级进程之前将 featureCompatibilityVersion 显式设立为应用程序数据库正在运行的当前MongoDB版本。

这可以防止升级进程中Ops Manager和应用程序数据库之间潜在的数据错位问题。

1 apiVersion: mongodb.com/v1
2 kind: MongoDBOpsManager
3 metadata:
4  name: om
5 spec:
6  topology: SingleCluster # optional, SingleCluster by default
7  opsManagerURL: https://link.to.configured.load-balancer.example.com # optional OM URL for the operator
8 replicas: 1
9 version: "8.0.0"
10  adminCredentials: ops-manager-admin-secret
11  configuration:
12   mms.fromEmailAddr: admin@example.com
13   mms.security.allowCORS: "false"
14  security:
15    tls:
16      ca: issuer-ca
17  backup:
18   enabled: true
19   encryption:
20     kmip:
21       server:
22         url: kmip.corp.mongodb.com:5696
23         ca: mongodb-kmip-certificate-authority-pem
24   headDB:
25    storage: "30Gi"
26    labelSelector:
27     matchLabels:
28      app: my-app
29   opLogStores:
30    - name: oplog1
31                        # Sets labels for the oplog store.
32      assignmentLabels: ["test1", "test2"]
33      mongodbResourceRef:
34       name: my-oplog-db
35      mongodbUserRef:
36       name: my-oplog-user
37   s3Stores:
38    - name: s3store1
39                        # Sets labels for the S3 store.
40      assignmentLabels: ["test1", "test2"]
41                        
42      mongodbResourceRef:
43       name: my-s3-metadata-db
44      mongodbUserRef:
45       name: my-s3-store-user
46      s3SecretRef:
47        name: my-s3-credentials
48      pathStyleAccessEnabled: true
49      s3BucketEndpoint: s3.region.amazonaws.com
50      s3BucketName: my-bucket
51  applicationDatabase:
52    passwordSecretKeyRef:
53     name: om-db-user-secret
54     key: password
55    members: 3
56    topology: SingleCluster
57    version: "7.0.21-ubi8"
58    featureCompatibilityVersion: "6.0" # During upgrade, set this FCV value to your currently deployed AppDB version.
59    security:
60      certsSecretPrefix: appdb
61      tls:
62        ca: issuer-ca

将配置重新应用于 Kubernetes。

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

Kubernetes 会使用新规范自动重新配置您的部署。您可以在MongoDB Ops Manager或Cloud Manager应用程序中看到这些更改的反映。

后退

使用本地模式

来年

1	apiVersion: mongodb.com/v1
2	kind: MongoDBOpsManager
3	metadata:
4	name: om
5	spec:
6	topology: SingleCluster # optional, SingleCluster by default
7	opsManagerURL: https://link.to.configured.load-balancer.example.com # optional OM URL for the operator
8	replicas: 1
9	version: "8.0.0"
10	adminCredentials: ops-manager-admin-secret
11	configuration:
12	mms.fromEmailAddr: admin@example.com
13	mms.security.allowCORS: "false"
14	security:
15	tls:
16	ca: issuer-ca
17	backup:
18	enabled: true
19	encryption:
20	kmip:
21	server:
22	url: kmip.corp.mongodb.com:5696
23	ca: mongodb-kmip-certificate-authority-pem
24	headDB:
25	storage: "30Gi"
26	labelSelector:
27	matchLabels:
28	app: my-app
29	opLogStores:
30	- name: oplog1
31	# Sets labels for the oplog store.
32	assignmentLabels: ["test1", "test2"]
33	mongodbResourceRef:
34	name: my-oplog-db
35	mongodbUserRef:
36	name: my-oplog-user
37	s3Stores:
38	- name: s3store1
39	# Sets labels for the S3 store.
40	assignmentLabels: ["test1", "test2"]
41
42	mongodbResourceRef:
43	name: my-s3-metadata-db
44	mongodbUserRef:
45	name: my-s3-store-user
46	s3SecretRef:
47	name: my-s3-credentials
48	pathStyleAccessEnabled: true
49	s3BucketEndpoint: s3.region.amazonaws.com
50	s3BucketName: my-bucket
51	applicationDatabase:
52	passwordSecretKeyRef:
53	name: om-db-user-secret
54	key: password
55	members: 3
56	topology: SingleCluster
57	version: "7.0.21-ubi8"
58	featureCompatibilityVersion: "6.0" # During upgrade, set this FCV value to your currently deployed AppDB version.
59	security:
60	certsSecretPrefix: appdb
61	tls:
62	ca: issuer-ca