Upgrading the custom resource

You can upgrade the custom resource to a new version by using a script or by following manual instructions.

Before you begin

Make a backup of your content services configuration volumes and folders, your Content Cortex domain and data, and the components in your IBM Content Navigator container environment. For more information, see Backing up the data in your Content Cortex domain and Backup and recovery of components in IBM Content Navigator container environment External link opens a new window or tab

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.