Preparing to upgrade your deployment

Before you upgrade the deployment, you must complete several steps to prepare your Content Platform Engine for upgrade.

About this task

The procedure assumes that you have all the components in a content services container environment. If you do not use any of the components, skip the steps for the components that do not apply.

You need to plan for upgrade at a time when you can restrict all user access to the content services container environment. When you upgrade the container images, make sure that you do all the standard checks and post upgrade configuration tasks. When you do all the checks, you can confirm that the content services container environment works the same way as it was before upgrade.

Important: Create a full backup of databases, volumes, and configuration files that can help you roll back your upgrade if needed.

Procedure

To prepare your deployment for upgrade:

  1. Disable the CBRdispatcher.
  2. If you have not already done so, make a backup of your databases and environment volumes.
  3. Confirm that you have a backup of the custom resource YAML file that you used to deploy FileNet Content Manager.
  4. Skip step 5, if you already ran the upgradedeployment.py script in deployment mode.
  5. Scale down the operator first, then your other components.
    Important: Make sure that you scale down your deployment before you apply the updated custom resources.
    To scale down a specific deployment (for Content Platform Engine, Business Automation Navigator, and Content Search Services):
    kubectl scale --replicas=0 deployment my_deployment_name -n my_project_name

What to do next

As a next step, you need to upgrade the operator version. For more information, see Upgrading the operator version and your components.

When the deployment is available, you can verify the upgrade. For more information, see the topic Verifying the upgrade.