Updating your Deployment

Updating your Deployment

Turbonomic will issue updates that provide fixes and new feature enhancements. Review what is in each version in the Release Notes published online. The upgrade process is as simple as supplying the right version to the Custom Resource. If you have any questions regarding versions and updates, contact Turbonomic support.

Updating via the OpenShift Operator Hub

If you have deployed the Turbonomic Server via the Operator Hub, then to upgrade, you should follow the path to first update the installed operator, which will then pull in both the latest operator and server version available (images stored in the Red Hat Container Catalog).

If you desire to upgrade to a different version than latest, you can. First, upgrade the installed operator to latest which will pull in the latest version of the operator. To define the specific version of Turbonomic Server, modify the installed instance (default is "xl-release")by selecting the installed instance -> YAML and modify the tag parameter under the global values:

  global:
    tag: 8.9.1

Updating via the YAML method

If you have deployed the Turbonomic Server via YAMLs, then you can upgrade by modifying the operator and the custom resource that defines your Turbo Server configurations including version.

Steps to update:

1. Review Release Notes to determine version required, and any additional configuration steps that may be required.
2. Check to see if the Operator needs to be updated. This step will be done first. Refer to Updating the Turbonomic Operator below.
3. If using a private registry, stage the images.
4. You will get the yamls used for:
   • Operator deployment (t8c-operator)
   • Custom Resources (default is xl-release)
5. If required, this step needs to be done before updating the platform. Edit the operator deployment yaml with the image tag required. Note the default image pull policy is Always.
   • Modify the image information and save:

      containers:
      - name: t8c-operator
        image: icr.io/cpopen/t8c-operator:42.30

6. Apply the yaml file.
   • Confirm the operator pod restarted, and is running.
7. Edit the custom resource.
   • Modify the tag under the global values:

  global:
    repository: icr.io/cpopen/turbonomic
    pullPolicy: Always
    tag: 8.9.1

8. Apply the yaml file.
   • All the pods except the operator will restart. When all the pods are in a running and ready state (1/1), then the migration is complete, and you can log in.

Updating KubeTurbo

When you have updated the Turbonomic platform you should also update KubeTurbo remote probes to stay aligned with the same version.

The image tag used will depend on your Turbo Server version. Go here to identify the version you need for CWOM -> Turbonomic Server -> KubeTurbo version.

The method used to update KubeTurbo will depend on the method used to deploy. Update instructions can be found at the end of the method used:

1. Helm Chart
2. Deploy Resources via yaml
3. Operator
4. Operator via Operator Hub

Update the Turbonomic Server first then update all the KubeTurbo's (one in each cluster).

Updating the Turbonomic Operator

Turbonomic is deployed and managed through an Operator (t8c-operator), and given the Operator contains definitions of component configurations, updates to the Turbo Server may require the Operator to be updated FIRST.

Check the instructions in theServer and Operator Version to see if a newer Operator version is required. If the Operator needs to be updated, do this FIRST. Edit the t8c-operator deployment resource with the new image tag.

Server and Operator Version

Turbonomic Operator Version required by Turbonomic Server version is reported in Release Notes.

Note, if you deployed Turbonomic on OpenShift 4.x via the Operator Hub, you should always keep the operator at the latest version regardless of the Turbonomic Server version you are running. The latest version of the operator can manage older product versions of the server.

1. Go to Turbonomic Documentation online
2. Selected the latest Turbonomic Application Resource Management product version
3. Select Release Notes
4. In Release Notes go to "Configuration Requirements" and then "Turbonomic Updates and Operator Version"