Upgrading the Operators

First upgrade both the IBM Sterling Intelligent Promising Operator and IBM OMS Gateway Operator, one after the other to upgrade IBM Sterling Intelligent Promising.

Before you begin

Upgrading to 10.0.2406.0-amd64
If you are upgrading the IBM Sterling Intelligent Promising to 10.0.2406.0-amd64, you must create a job column in inv_upgrade table. For more information, see Prerequisites for upgrading to 10.0.2406.0-amd64.
Upgrading to any other version
Continue to complete the steps that are given in the following procedure.

About this task

Based on the Registry poll interval provided in the subscription, the cluster looks for new version of the Operator periodically. Whenever an upgrade is available for the subscribed channel, the Operator either automatically upgrades or wait for manual approval, based on the selected Update approval strategy.
When you create a subscription for the Sterling Intelligent Promising Operator and OMS Gateway Operator, you can choose automatic or manual updates approval strategy. For more information about creating a subscription, see step 3.
Automatic approval strategy
If you choose automatic updates for an installed Operator, when a new version of that Operator is available in the selected channel, Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without human intervention.
Manual approval strategy
If you select manual updates, when a newer version of an Operator is available, OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Operator that is updated to the new version.
Attention: It is recommended to not configure the upgrade policy to Automatic. Set it to Manual to ensure controlled and validated upgrades of Sterling Intelligent Promising components. Automatic upgrades may lead to unexpected service disruptions and compatibility issues. Manual upgrade policy allows for proper planning, testing, and validation before applying updates to production environments.
Note: In the following procedure, you can use either oc or kubectl commands.

Procedure

  1. Get the install plan. If your Registry poll interval is set to automatic, skip step 1 and step 2. 
    oc get installplan -n <namespace>
  2. Approve the install plan. 
    oc patch installplan <INSTALL_PLAN_NAME> -n <namespace> --type merge --patch '{"spec":{"approved":true}}'
  3. Verify the version of both the Operators, after the Operators are upgraded. 
    oc get clusterServiceVersion -n <namespace>
    The output of the command is shown in the following snippet.
    NAME                     DISPLAY                                                  VERSION   REPLACES                 PHASE
ibm-oms-gateway.v1.0.4   IBM Sterling Order Management Gateway Standard package   1.0.4     ibm-oms-gateway.v1.0.3   Succeeded
ibm-sip.v1.0.4           IBM Sterling Intelligent Promising Standard package      1.0.4     ibm-sip.v1.0.3           Succeeded