Upgrading Product Master Kubernetes or Red Hat OpenShift deployment

This topic explains the procedure to migrate Kubernetes or Red Hat® OpenShift® cluster.

Before you begin

Fix Pack 7 and later

Ensure that the Container system requirements are met.
Download the Product Master docker assets. For more information, see Downloading images by using your own Docker registry.
Ensure that you have all the product deployment files for your current fix pack version. Download all the latest fix pack release deployment files from the IBM® Support Fix Central site.
Ensure that you understand how the Product Master is installed by using operators. For more information, see Installing the product by using Operators.
Ensure that deployment YAML files are configured. For more information, see Configuring Product Master deployment YAML (Fix Pack 7 and later).

Procedure

Verify that the secret details are present by using the following command.

# oc get secret  | grep ipm-registry

# oc get secret  | grep 'app-secret\|tls-secret’

Take backup of the existing release deployment files, customization, app-secret, random-secret, IBM Db2® database and MongoDB, and /opt/MDM/public_html folder of admin pod.
To take backup of MongoDB proceed as follows:
1. Go to the MongoDB pod by using the following command.
```
# oc rsh productmaster-mongodb-5464cb968-qcnts
```
  Note: Get the MongoDB user and password through the random-secret file.
2. Take the backup of the MongoDB database by using the following command.
```
$cd /data/db
$mongodump \ 
--username <username> \
--authenticationDatabase admin \ 
--password <password> \ 
-d <database_name>
```
3. Download the /data/db/dump folder to your local machine by using the following command.
```
oc rsync productmaster-mongodb-6975f78c4d-4hx5w:/data/db/dump .
```
Check the CR name by using the following command.
```
# oc get productmaster
```
Note: You need to use the same CR name in the ipm_12.0.x_cr.yaml file.
Update the ipm_12.0.x_cr.yaml file to make replica count of all pods to 0 and apply again.
Confirm that all the pods are removed by using the following command.
```
# oc get pods
```
Optional: If you have created any manual ingress route for IBM Product Master, delete it by using the following command.
```
# oc delete ingress <name>
```
Check existing packagemanifest before applying subscription by using the following command.
```
# oc describe packagemanifest productmaster-operator | grep -C3 "Default Channel"
```
Update the new catalog source docker images into the catalog_source.yaml ﬁle. You can ﬁnd the new image in the latest downloaded catalog_source.yaml ﬁle (IBM Product Master deployment ﬁles that are downloaded from the IBM Support Fix Central site).
Apply the catalog_source.yaml ﬁle by using the following command.
```
# oc apply -f catalog_source.yaml
```
1. Verify creation of new pods starts by using the following command.
```
# oc get pods
```
2. Verify that the new catalog is created by using the following command.
```
# oc get pods | grep catalog
```
3. Verify that the packagemanifest is updated with the new channel version and operator image by using the following command.
```
# oc describe packagemanifest productmaster-operator | grep -C3 "Default Channel"
```
Update CSV or Operator controller. This step is required only if you have set the value of InstallPlanApproval to Manual because when the value is Automatic, subscription gets updated automatically.

Add the volume details for the new magento and message-archive services as follows in your volumes.yaml file.


kind: PersistentVolume
apiVersion: v1
metadata:
  name: magento-connector-log-volume
  namespace: default
  labels:
    svc: magento-connector-log-volume
spec:
  capacity:
    storage: 2Gi
  accessModes:
    - ReadWriteOnce
  storageClassName: standard
  hostPath:
    path: /mnt/ipm12/magento-connector

You can copy this message block also from the volumes.yaml file downloaded from the IBM Support Fix Central site).

What to do next

Upgrade IBM Product Master by using the newly downloaded ipm_12.0.x_cr.yaml file as follows.

Update the storage class to the same value as used in the IBM Product Master your current fix pack deployment.
Optional:If you are using own registry, update the value of the image > registry.

Ensure that the CR name for both releases is the same.


apiVersion: productmaster.ibm.com/v1
kind: ProductMaster
metadata:
  name: <CR name>

Update all the changes that you need in your new CR including storage type including the new service for Magento Connector.
Enable feature that are required and mark rest of 0 so that associated pods don't come up and consume CPU and Memory. For more information, see con_oper_custmfeature.html.
Apply the CR file. After all the pods are up and running, you can log in to the IBM Product Master by using the same login URLs that you used for the IBM Product Master your current fix pack version.
If you are using dynamic volume provisioning then you need to perform following steps for MongoDB backup and restore. You need to restore the MongoDB database that you backed up in the MongoDB backup section.
1. Copy dump into the /data/db folder of the MongoDB pod by using the following command.
```
# oc rsync dump productmaster-mongodb-0:/data/db
```
2. Restore the MongoDB database by using the following command.
```
$ mongorestore 
--username <username> \  
--authenticationDatabase admin \
--password <password> \  
/data/db/dump
```
Performing database migration.
1. Access the productmaster-admin-<container-name> pod by using the following command.
```
# oc rsh productmaster-admin-<container-name>
```
2. Run the migrateToInstalledFP.sh script file in the $TOP/bin/migration folder by using the following command.
```
migrateToInstalledFP.sh 
--fromversion=<fixpackversion>
```
Fix Pack 6If you had done the customization by creating custom images, then to get your customizations, you now need to follow Customizing the containerized deployment instructions.