Performing a major version upgrade
You can upgrade your container deployments to the latest version by deploying new versions of the container images.
Before you begin
Consult with your database administrator to determine whether your databases also require an
upgrade to support your new target version. If so, complete your database upgrades before you start
the container upgrade.
Tip: You can optionally run the must_gather.py
script to collect all information about your deployment before upgrade. For more information, see
topic Must Gather.
Important: During a major version upgrade, the FNCMCluster custom resource definition,
which is shared across the cluster, can be affected. For a smooth transition from a prior release,
the custom resources for deployments on the prior release must be edited and applied before the
operator and custom resource definition are upgraded.
The operator is upgraded when either the
deploy_operator.py script is run or for OpenShift® based environments, the new catalog source is applied by using the OCP
console.
About this task
Check the IBM Software Product Compatibility Report for the
appropriate versions of supporting software.
Important:
- If you are starting from v5.5.7 and below, you must upgrade to v5.5.8 first.
- If you are starting from v5.5.11 and below, you must upgrade to v5.5.12 first.
- If you are starting from v5.5.12 and above, you can directly upgrade to v26.0.0.
To minimize the upgrade time for your object stores, follow the suggested best practices before
upgrading to v5.5.9 or higher. For more information, see the technote Best Practice:
Upgrading to Content Platform Engine V5.5.9 or higher
.
While you are upgrading your container environment, you must restrict all user access to the content services. Be sure to plan the upgrade for a time when it is most convenient for your users.