Performing a minor version update
Updates to container deployments are delivered as interim fixes.
About this task
Three distinct procedures exist to deploy your content services containers. Installation and upgrade both involve the deployment of a new major release version.
An update, however, refers to deploying an interim or test fix on top of an existing FileNet® Content Manager V5.6.0 container deployment. For example, moving from Content Platform Engine V5.6.0 container version to CPE 5.6.0.0-P8CPE-IF001 container version is defined as an update.
Updates provide fixes and improvements to an installed release, while maintaining the level of the release. Updates are usually cumulative, so you can install the latest available update to obtain all fixes going back to the original release level. You can optionally make a backup of the FileNet P8 domain and data. For more information, see Backing up the data in your FileNet P8 domain and Backup and recovery of components in IBM Content Navigator container environment. You can roll the deployment back to another minor version within the same major release without restoring the data from backup. You can apply the minor version update as a rolling update by using the commonly accepted methodologies available in Kubernetes.
Even if you are installing for the first time, check Fix Central to see what updates are available and apply them to your new installation. Applying updates ensures that your installation has all the most recent fixes and improvements that are available.
For information about the high-level process to update an environment with interim fixes, see support document Updating containerized FileNet Content Manager deployments with interim fixes.
The steps that are covered in the Updating containerized FileNet Content Manager deployments with interim fixes technote include:
- Downloading the
container-samples
repository for the interim fix - Get access to the interim fix container images
- Option A: Online Deployment
- Option B: Offline Deployment on OCP using Air gap
- Option C: Offline Deployment on CNCF Platforms using Private Registry
- Update the installed operator
- Option A: Online Operator Upgrade using the Red Hat OpenShift console
- Option B: Online Operator Upgrade by running a script
- Option C: Online Operator Upgrade using YAML (OCP Only)
- Option D: Online Operator Upgrade using YAML (CNCF Only)
- Option E: Offline Operator Upgrade on OCP using Air gap
- Option F: Offline Operator Upgrade on CNCF Platforms using Private Registry
- [Optional] Update the custom resource YAML file for your FileNet Content Manager deployment
- Verify the updated containers