Upgrading the IBM Cloud Private

You can upgrade the IBM Cloud Private from specific previous versions.

This procedure is intended for users with role cloud administrator.

The supported upgrade paths are:

• IBM Cloud Private version 3.1.1 to 3.1.2
• IBM Cloud Private version 3.1.1 to 3.2.0
• IBM Cloud Private version 3.1.2 to 3.2.0

Procedure

1. Depending on the IBM Cloud Private release you have installed, follow the instructions to complete the upgrade.

   • For IBM Cloud Private Community edition, see Upgrading IBM Cloud Private-CE.
   • For IBM Cloud Private Enterprise edition, see Upgrading IBM Cloud Private.

2. After the upgrade is completed, clean up the temporary files that are created during the Secure Service Container for IBM Cloud Private upgrade by using the CLI tool.

   ${pwd}./ssc4icp-cli-installer-upgrade-<version>.sh clean_up
   

   Note:

   • The cleanup command must be executed under the /config directory of the Secure Service Container for IBM Cloud Private installation directory.
   • You must replace the <version> with the correct CLI version number. For example, 1.1.0.3.

3. To dynamically update the CPU or memory resources on the cluster nodes, complete the following steps.

   1. Create a tmp directory in the home directory, and go to this tmp directory.

      mkdir ~/tmp && cd tmp
      

   2. Download the configuration template files into the tmp directory.

      docker run --network=host --rm -v $(pwd):/data ibmzcontainers/ssc4icp-cli-installer:1.1.0.3 cp -r config /data
      

   3. Copy the ssc4icp-config-update.yaml file into the Secure Service Container for IBM Cloud Private installation directory.

      cp config/ssc4icp-update.yaml to the SSC4ICP_INSTALLATION_FOLDER/config/
      

   4. (Optional) Update the resources for the cluster nodes. For more information, see Updating the cluster resources dynamically.