If you use IBM Storage Fusion, NetApp Astra Control Center, or Portworx to back up and restore your Cloud Pak for Data deployment, you must upgrade the cpdbr service after you upgrade Cloud Pak for Data.
- Who needs to complete this task?
-
Cluster administrator A cluster administrator
must complete this task.
- When do you need to complete this task?
-
You must complete this task if you back up your deployment on the following storage providers:
- IBM Storage Fusion
- NetApp Astra Control Center
- Portworx
Repeat as needed If you have multiple instances
of Cloud Pak for Data, repeat this task for each instance
that you upgrade.
Before you begin
Best practice: You can run many of
the commands in this task exactly as written using the installation environment variables. Ensure
that you added the new environment variables from
Updating
your environment variables script.
In addition, ensure that you source the environment
variables before you run the commands in this task.
About this task
After you upgrade Cloud Pak for Data, you must upgrade the cpdbr service image.
Procedure
- Patch the
cpdbr-tenant-service
Deployment in the operators project for the instance of
Cloud Pak for Data that you upgraded. The
command that you run depends on where your cluster pulls images from and your cluster hardware:
- The cluster pulls images from the IBM
Entitled Registry
-
x86_64 clusters
oc patch deployment cpdbr-tenant-service \
--namespace=${PROJECT_CPD_INST_OPERATORS} \
--type=json \
--patch="[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\": \"icr.io/cpopen/cpd/cpdbr-oadp:${VERSION}-x86_64\"}]"
ppc64le clusters
oc patch deployment cpdbr-tenant-service \
--namespace=${PROJECT_CPD_INST_OPERATORS} \
--type=json \
--patch="[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\": \"icr.io/cpopen/cpd/cpdbr-oadp:${VERSION}-ppc64le\"}]"
s390x clusters
oc patch deployment cpdbr-tenant-service \
--namespace=${PROJECT_CPD_INST_OPERATORS} \
--type=json \
--patch="[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\": \"icr.io/cpopen/cpd/cpdbr-oadp:${VERSION}-s390x\"}]"
- The cluster pulls images from a private container registry
-
x86_64 clusters
oc patch deployment cpdbr-tenant-service \
--namespace=${PROJECT_CPD_INST_OPERATORS} \
--type=json \
--patch="[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\": \"${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/cpdbr-oadp:${VERSION}-x86_64\"}]"
ppc64le clusters
oc patch deployment cpdbr-tenant-service \
--namespace=${PROJECT_CPD_INST_OPERATORS} \
--type=json \
--patch="[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\": \"${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/cpdbr-oadp:${VERSION}-ppc64le\"}]"
s390x clusters
oc patch deployment cpdbr-tenant-service \
--namespace=${PROJECT_CPD_INST_OPERATORS} \
--type=json \
--patch="[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\": \"${PRIVATE_REGISTRY_LOCATION}/cpopen/cpd/cpdbr-oadp:${VERSION}-s390x\"}]"
- Reinstall the
cpdbr-tenant component for the instance. The
command that you run depends on the type of storage that you use, where the cluster pulls images
from, and whether the
scheduling service is installed:
- IBM Storage Fusion
-
The cluster pulls images from the IBM
Entitled Registry
- Environments with the scheduling service
- Run the appropriate command based on the version of Cloud Pak for Data that is installed on your
cluster:
cpd-cli oadp install \
--component=cpdbr-tenant \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=icr.io/cpopen/cpd \
--cpd-scheduler-namespace=${PROJECT_SCHEDULING_SERVICE} \
--recipe-type=br \
--log-level=debug \
--verbose
- Environments without the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=icr.io/cpopen/cpd \
--recipe-type=br \
--log-level=debug \
--verbose
The cluster pulls images from a private container registry
- Environments with the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=${PRIVATE_REGISTRY_LOCATION} \
--cpd-scheduler-namespace=${PROJECT_SCHEDULING_SERVICE} \
--recipe-type=br \
--log-level=debug \
--verbose
- Environments without the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=${PRIVATE_REGISTRY_LOCATION} \
--recipe-type=br \
--log-level=debug \
--verbose
- NetApp Astra Control Center
-
The cluster pulls images from the IBM
Entitled Registry
- Environments with the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=icr.io/cpopen/cpd \
--cpd-scheduler-namespace=${PROJECT_SCHEDULING_SERVICE} \
--log-level=debug \
--rbac-only=true \
--verbose
- Environments without the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=icr.io/cpopen/cpd \
--log-level=debug \
--rbac-only=true \
--verbose
The cluster pulls images from a private container registry
- Environments with the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=${PRIVATE_REGISTRY_LOCATION} \
--cpd-scheduler-namespace=${PROJECT_SCHEDULING_SERVICE} \
--log-level=debug \
--rbac-only=true \
--verbose
- Environments without the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=${PRIVATE_REGISTRY_LOCATION} \
--log-level=debug \
--rbac-only=true \
--verbose
- Portworx
-
The cluster pulls images from the IBM
Entitled Registry
- Environments with the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=icr.io/cpopen/cpd \
--cpd-scheduler-namespace=${PROJECT_SCHEDULING_SERVICE} \
--log-level=debug \
--rbac-only=true \
--verbose
- Environments without the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=icr.io/cpopen/cpd \
--log-level=debug \
--rbac-only=true \
--verbose
The cluster pulls images from a private container registry
- Environments with the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=${PRIVATE_REGISTRY_LOCATION} \
--cpd-scheduler-namespace=${PROJECT_SCHEDULING_SERVICE} \
--log-level=debug \
--rbac-only=true \
--verbose
- Environments without the scheduling service
-
cpd-cli oadp install \
--component=cpdbr-tenant \
--namespace=${OADP_OPERATOR_NS} \
--tenant-operator-namespace=${PROJECT_CPD_INST_OPERATORS} \
--cpdbr-hooks-image-prefix=${PRIVATE_REGISTRY_LOCATION} \
--log-level=debug \
--rbac-only=true \
--verbose
What to do next
Your next steps depend on which components you upgraded when you completed Upgrading IBM Cloud Pak for Data (Upgrading from Version 5.0.x to a later 5.0 refresh):
- Cloud Pak for Data control
plane and services
- If you upgraded the Cloud Pak for Data control
plane and
the services in the instance, see Setting up services after install or upgrade.
- Cloud Pak for Data control
plane only
- If you upgraded only the Cloud Pak for Data control
plane, you must upgrade the services in the instance. For more information, see Services.