Updating the Kubeturbo version through an operator

Update the image tag version of your Kubeturbo deployment whenever your Turbonomic instance updates to a new version or if you are instructed to do so.

The image tag version should be in the format x.x.x. This version depends on, and should always match, your Turbonomic instance version. For example, if your Turbonomic instance version is 8.15.0, specify the same instance version as the image tag version.

To get the version of your Turbonomic instance, open the Turbonomic user interface and click the Help icon in the navigation menu.

There are several ways to update the Kubeturbo deployment.

  • Update your manifest.

  • Update the running Kubeturbo deployment resource.

Updating your manifest

  1. Edit the original custom resource used to deploy Kubeturbo. For example, if you downloaded the YAML resource for the cluster-admin role, edit deploy/kubeturbo_yamls/turbo_kubeturbo_operator_full.yaml.

    Update the following parameter:

    image: icr.io/cpopen/kubeturbo-operator:{new_image_tag_version}
  2. (Optional) If you are using a private repository, update the following parameter:

    tag: {new_image_tag_version}
  3. Apply the change to the operator.

    kubectl apply -f deploy/kubeturbo_yamls/{YAML_resource}

    For example:

    kubectl apply -f deploy/kubeturbo_yamls/turbo_kubeturbo_operator_full.yaml

Repeat these steps for every cluster with a Kubeturbo deployment.

Updating the running Kubeturbo deployment resource

  1. If you do not have the original custom resource used to deploy Kubeturbo, you can edit Kubeturbo directly by running the following command:

    kubectl edit deployment kubeturbo-operator
  2. Specify the image tag version in the image: parameter.

    image: icr.io/cpopen/kubeturbo-operator:{new_image_tag_version}
  3. (Optional) If you are using a private repository, update the following parameter:

    tag: {new_image_tag_version}

After you save your changes, the Kubeturbo pod redeploys.

Repeat these steps for every cluster with a Kubeturbo deployment.

Updating when using a non-default cluster role

If you are updating from Kubeturbo 8.9.6 or earlier and are using a non-default cluster role, such as turbo-cluster-reader or turbo-cluster-admin, perform the following steps after you update Turbonomic to ensure that your deployment uses the updated cluster role names and to avoid errors.

  1. Delete all cluster roles that start with the names turbo-cluster-reader and turbo-cluster-admin. There could be four cluster roles with such names.

  2. Delete any cluster role binding that starts with the name turbo-all-binding-kubeturbo.

After a few minutes, the kubeturbo-operator automatically recreates the required non-default cluster role and cluster role binding using the new names.