Upgrading Cloud Pak for Data System

This section describes how to upgrade Cloud Pak for Data System.

Important: The support team cannot assist with any issues that are related to OCP version 4.10 and earlier along with compatible CPD versions. It is recommended to use the latest OCP version with compatible CPD versions as listed in the product matrix. To upgrade OCP, you must have Cloud Pak for Data System 2.0.2.1 or later.
The following table presents which Cloud Pak for Data System components are upgraded in each release, and the upgrade path for each release.
Table 1. Certified Cloud Pak for Data System upgrades
Cloud Pak for Data System Red Hat® OpenShift® Container Platform Red Hat Enterprise Linux® OpenShift Data Foundation Cloud Pak for Data Netezza® Performance Server Cumulus Python Upgrade path
2.0.0.0 4.6.32 8.2 4.6.5 4.0.1 11.2.2.0 3.7.11 3.6.8 Fresh installation only
2.0.1.0 4.6.32 8.2 4.6.5 4.0.2 11.2.2.0 3.7.11 3.6.8
  • Fresh installation
  • Advanced upgrade from 1.0.7.6 for Cloud Pak for Data customers
  • Advanced upgrade from 1.0.7.x for Netezza Performance Server customers
2.0.1.1 4.6.32 8.2 4.6.8 4.0.2 11.2.2.1 3.7.11 3.6.8
  • Fresh installation
  • Advanced upgrade from 1.0.7.6
2.0.2 4.8.37 8.5 4.8.7 4.0.2 11.2.2.3 3.7.11 3.6.8
  • Fresh installation
  • Advanced upgrade from 1.0.7.6
  • Upgrade from 2.0.1.1
2.0.2.1 4.8.37 8.6 4.8.7 4.0.2 11.2.2.4 3.7.11 3.6.8
  • Fresh installation
  • Advanced upgrade from 1.0.7.6
  • Upgrade from 2.0.1.1
2.0.2.1 4.10.64 8.6 4.10.14 4.0.2 11.2.2.4 3.7.11 3.6.8
  • Fresh installation
  • Advanced upgrade from 1.0.7.6
  • Upgrade from 2.0.1.1
2.0.2.1 4.12.30 8.6 4.12.7-rhodf 4.7.x* and 4.8.x* 11.2.2.4 3.7.11 3.6.8
  • Advanced upgrade from 1.0.7.6
  • Upgrade from 2.0.1.1
Important: You must upgrade to Cyclops 4.0 before upgrading Red Hat OpenShift Container Platform (OCP) and OpenShift Data Foundation (ODF) to version 4.10. For installation instructions, see the README file.
4.10 upgrade
To upgrade OCP and OCS to version 4.10, see OCP and OCS upgrade in a connected environment by using Red Hat OpenShift console UI.
4.12 upgrade
*Cloud Pak for Data
To know more about Upgrading to Cloud Pak for Data 4.7.x versions, see Upgrading from IBM Cloud Pak for Data Version 4.7.x to a later 4.7 refresh.
To know more about Upgrading to Cloud Pak for Data 4.8.x versions, see Upgrading from IBM Cloud Pak for Data Version 4.8.x to a later 4.8 refresh.
Jump upgrades are not possible with OCP and ODF. For example, if you are in version 4.10 and want to upgrade to version 4.12, you must upgrade to version 4.11 and then to 4.12.

Before you begin

Before you start the upgrade process, check the release notes to learn about any known issues or workarounds that pertain to the version you are upgrading to. See What's new in 2.0.
Note:
  • Cloud Pak for Data upgrade is bundled with the system upgrade package and is part of the upgrade process.
  • Do not upgrade any Cloud Pak for Data services before you upgrade Cloud Pak for Data System. This might cause the system upgrade to fail. If you have already upgraded some of the services, contact IBM Support before upgrading the system.
  • If the system has any user-managed Cloud Pak for Data tenants (on the namespace other than zen or ap-console), those tenants will be upgraded during the service bundle upgrade automatically, unless you pin the installation to a specific version in the ZenService custom resource. For moreinformation, see the Manual upgrade section in Choosing an upgrade plan for the Cloud Pak for Data control plane.
  • Netezza Performance Server and Cloud Pak for Data System releases are independent.

    The Netezza Performance Server release that is mentioned in the table is the latest release that was available at the time, but it does not mean that only this release is supported. It is always recommended to have the latest Netezza Performance Server/Cloud Pak for Data System version.

About this task

IBM Support will assist you in upgrading Cloud Pak for Data System from version 1.x to version 2.x. Contact your IBM representative for details.