Upgrading IBM Enterprise Records

If you deployed Enterprise Records, you must upgrade the ier_configuration section in the custom resource YAML file that is used in the previous version.

Before you begin

The custom resource file includes several mandatory configuration parameters. Depending on the version of your custom resource YAML file, you must add these mandatory parameters to the file, or provide specific values for parameters that previously used the default value. For more information about these parameters see the IBM Enterprise Records parameters.

Important: To roll back your upgrade if needed, take a backup of persistent volume and configuration files that you created in Step 1 of Procedure section in Option 1: Creating the persistent volume (PV) and the persistent volume claim (PVC) manually.

About this task

By default, the operator deploys each container by using the image digests that correspond to the image tags in the following table. If you want to override the image digest with a specific image tag (for example, to apply an interim fix), you can specify the image tag in the custom resource (CR).
Table 1. Docker image changes in operator 23.0.2
Operator version Configuration parameter Value
23.0.2 image.tag If your custom resource does not include this parameter, you can safely ignore it. If you have an image tag, either remove it from the CR or set the value to the new image tag "23.0.2".
Remember: Be sure to plan the timing of the upgrade to ensure minimal disruption to your users.

Procedure

  1. Take a backup of the custom resource YAML file that you used to deploy Enterprise Records.
  2. In the new working copy of your custom resource file, make sure that the spec section includes all of the mandatory new parameters.

What to do next

Plan your upgrade for a time when it is convenient to restrict all user access to content services. During the process of upgrading your container images, you must also perform the standard checks and post upgrade configuration tasks to ensure that your content services environment continues to function as it did before the upgrade.

Apply the updated custom resource YAML file as described in Applying the updated custom resource.

When the deployments are available, verify the upgrade by using the instructions in Verifying the Enterprise Records upgrade.