Upgrading your IBM Cloud Pak® deployment from 25.0.0

Update the version of your Cloud Pak for Business Automation deployments from 25.0.0-IF004 or later to 26.0.0 in the YAML definitions. Each pod with the old version is deactivated, and an updated pod is created with the new version to replace it. The workload is transferred one-by-one from the old pods to the new pods.

Before you begin

Tip: The new version might introduce new parameters or require different values in the custom resource (CR) of your CP4BA deployment. To get a look at these changes, you can generate a CR file by using the deployment script from the new version and then compare your previous CR with the generated CR. If you do want to compare the CR files, it is important to choose the same capabilities and optional components in the new script that are included in your deployed CR. For more information about running the deployment script, see Generating the custom resource with the deployment script.

About this task

Upgrading can involve many manual steps when your deployment includes many capabilities and you have lots of traffic into and out of the cluster. You might need to stop all the traffic to the running applications before you apply an updated custom resource.

Important: Due to the number of dependencies that each pattern has it is advisable not to try to upgrade individual containers in your deployment. Upgrade everything within your deployment at the same time.