Atualize o Ops Manager e as versões de reconhecimento de data center de backup

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.

Pré-requisitos

Aviso

Para manter as configurações e a disponibilidade existentes, faça backup dos itens abaixo na sua instância atual do Ops Manager:

Seu conf-mms.properties em um local seguro. O conf-mms.properties armazena configurações para a instância do 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.

Importante
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.
Se você precisar atualizar seus bancos de dados de apoio para uma versão compatível do MongoDB , consulte Atualizar versão do MongoDB .

Procedimento

Para atualizar o MongoDB Ops Manager e as versões do banco de dados do aplicativo, complete as seguintes etapas:

Na Especificação de recursos do Ops Manager, as configurações são mostradas no exemplo a seguir:

Configure spec.version para a nova versão do Ops Manager.
Se você atualizou o banco de dados do aplicativo, defina spec.applicationDatabase.version para a versão compatível do MongoDB.

Importante

Certifique-se de escolher uma versão compatível do MongoDB Server.

Versões compatíveis diferem dependendo da imagem base que o recurso do banco de dados MongoDB utiliza.

Aviso

Conforme o exemplo abaixo, como os recursos do banco de dados de aplicativo associados à implantação atual do Ops Manager são atualizados de forma contínua, você deve definir explicitamente o featureCompatibilityVersion para a versão atual do MongoDB que o banco de dados de aplicativo está executando antes de iniciar o processo de upgrade.

Isso evita possíveis problemas de desalinhamento de dados entre o Ops Manager e o banco de dados de aplicativo durante o processo de upgrade.

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

Reaplique a configuração ao Kubernetes.

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

O Kubernetes reconfigura automaticamente seu sistema com as novas especificações. Você pode ver essas alterações refletidas em seu aplicativo MongoDB Ops Manager ou Cloud Manager .

Voltar

Usar o modo local

Configurar queryable backups

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