Updating using the Red Hat OpenShift OperatorHub

Note:

Review What's New and Release Notes to see what is new for this release.

As Turbonomic evolves, the set of delivered probes change. When you update to a new version, the update does not change the properties of your Turbonomic instance or your probe configuration, as per what is defined in the Custom Resource. An update to a newer version does not automatically enable any new probes in your deployment. If you want to take advantage of new probes in an update, then you must enable them manually.

The steps to follow for updating your Turbonomic Platform depends on the Update approval strategy you specified when installing Turbonomic using the Red Hat OpenShift OperatorHub: Automatic or Manual. If you are unsure which approval strategy is in place, navigate to the Operators > Installed Operators > Turbonomic Platform Operator > Subscription tab. The Update approval strategy and Upgrade status are listed in the Subscription details section of the screen.

Note:

The Starting version listed on the Subscription tab indicates the Operator version, not the Turbonomic version. It is important to keep in mind that the Operator version does not drive the Turbonomic version. Although the Operator may be up to date, you must still manually update the Turbonomic server version for each update. See Updates and Operator Version for a listing of the product and Operator versions.

Automatic update approvals

If the Operator (or Turbonomic Platform Operator) Update approval strategy in the subscription is set to Automatic, the upgrade process initiates as soon as a new Operator version is available. In this case, you only need to update the Turbonomic version in the Custom Resource YAML.

Note:

You cannot revert the version of either the installed Operator or Turbonomic Platform.

The Turbonomic Platform Operator, starting with v42.22, is automatically updated to pull from the IBM Container Registry (icr.io/cpopen). Ensure your operator is updated to the latest version, and the XL CR (xl-release) repository is set to the IBM Container Registry.

  1. Select Operators > Installed Operators > Turbonomic Platform Operator.

  2. Click the Turbonomic Platform Operator link under the Provided APIs header, then click xl-release under the Name header.

  3. Click the YAML tab to open the Custom Resource YAML.

    (If not already done) Edit the Custom Resource YAML to change the repository parameter from the Red Hat Container Catalog to the IBM Container Registry (icr.io/cpopen).

    Edit the Custom Resource YAML to change the version in the tag:<version> parameter to the product version to which you want to upgrade.

    spec: 
  global:
    repository: icr.io/cpopen/turbonomic
    tag: <version>
    Note:

    The repository parameter must specify icr.io/cpopen/turbonomic as the repository location when working with Red Hat Operators.

  4. Click Save.

  5. Verify that the requested Turbonomic version installed correctly.

    Open the Workloads > Pods page to confirm all pods have a Status listed as Running, and that the Ready column shows the expected pods are fully up, for example 1/1, 2/2, and so on. The upgrade process may take several minutes to complete.

  6. If you are already logged into the Turbonomic UI, clear your browser data and refresh your browser, or open an incognito window.

    You now have full access to Turbonomic features. However, features that rely on current analysis data will not be available until after a full market cycle - usually 10 minutes. For example, the Pending Actions charts will not show any actions until after a full market cycle.

  7. Notify other users who access the Turbonomic UI to clear their browser data and refresh their Turbonomic browser sessions.

Manual update approvals

If the Update approval strategy in the subscription is set to Manual, you must first manually approve pending upgrades for the Turbonomic Operator (t8c-operator), then update the Turbonomic server version in the Custom Resource YAML. Check Updates and Operator Version for a listing of the Turbonomic and Operator versions.

Note:

The Turbonomic Platform Operator, starting with v42.22, is automatically updated to pull from the IBM Container Registry (icr.io/cpopen). Ensure your operator is updated to the latest version, and the XL CR (xl-release) repository is set to the IBM Container Registry.

  1. Select Operators > Installed Operators.

  2. Operators that have a pending upgrade display a status with "Upgrade available." Click Turbonomic Platform Operator.

  3. Select the Subscription tab. Any upgrades requiring approval are displayed next to Upgrade status. For example, it might display 1 requires approval.

  4. Click the Upgrade status link (for example, 1 requires approval), then click Preview Install Plan.

  5. Review the resources that are listed as available for upgrade. When satisfied, click Approve.

  6. Navigate back to the Operators > Installed Operators page to monitor the progress of the upgrade. When complete, the status changes to "Succeeded" and "Up to date."

    Note:

    You may be presented with another operator update.

  7. From the Installed Operators page, click Turbonomic Platform Operator > Turbonomic Platform Operator tab > xl-release.

  8. Click the YAML tab to open the Custom Resource .

    (If not already done) Edit the Custom Resource YAML to change the repository parameter from the Red Hat Container Catalog to the IBM Container Registry (icr.io/cpopen).

    Edit the Custom Resource YAML to change the version in the tag:<version> parameter to the product version to which you want to upgrade.

    spec: 
  global:
    repository: icr.io/cpopen/turbonomic
    tag: <version>
    Note:

    The repository parameter must specify icr.io/cpopen/turbonomic as the repository location when working with Red Hat Operators.

  9. Click Save.

  10. Verify that the requested Turbonomic version installed correctly.

    Open the Workloads > Pods page to confirm all pods have a Status listed as Running, and that the Ready column shows the expected pods are fully up, for example 1/1, 2/2, and so on. The upgrade process may take several minutes to complete.

  11. If you are already logged into the Turbonomic UI, clear your browser data and refresh your browser, or open an incognito window.

    You now have full access to Turbonomic features. However, features that rely on current analysis data will not be available until after a full market cycle - usually 10 minutes. For example, the Pending Actions charts will not show any actions until after a full market cycle.

  12. Notify other users who access the Turbonomic UI to clear their browser data and refresh their Turbonomic browser sessions.