Deployment Options

Kubeturbo Deployment

NOTE: All Kubeturbo deployment related documentation is now in the official IBM Docs here. This GitHub wiki is no longer being updated, please refer to the official IBM Docs going forward.

---

NOTE: New Kubeturbo versions are released with and match the Turbonomic Product Version, detailed here

---

There are four different deployment options for Kubeturbo: Helm chart, Yamls, Operator via Yamls, and Operator via Red Hat OpenShift Operator Hub.

This document gives a brief overview of each method, and links to articles that provide deployment details based on the method you want.

Please make sure to first review the following topics before deciding on a deployment method:

1. Prerequisites
2. Release Notes
3. Turbonomic - CWOM - Kubeturbo version mappings

Using a Helm Chart

Helm charts are an easy way to deploy and update kubeturbo. We provide you a helm chart when you git clone this project (under kubeturbo/deploy/kubeturbo/), index this chart as a local helm repo, and install. You will need to specify a few parameters to complete the install.

For more details go to Helm Deployment.

Deploy with YAMLs

You can deploy the kubeturbo probe and the related resources using yaml files (under kubeturbo/deploy/kubeturbo_yamls/) that define the resources required, along with an example of a single yaml to create all resources.

For more information, go to Yaml Deployment

Deploy with an Operator

A Kubeturbo Operator can be used to deploy kubeturbo. You can deploy the Operator, CRD and related resources such as a sample CR from the yaml files available (under kubeturbo/deploy/kubeturbo-operator/).

For details go to Operator Deployment.

Deploy with an Operator in OpenShift OperatorHub

For Red Hat OpenShift 4.x users, you can use the certified KubeTurbo Operator available via the OpenShift OperatorHub.

For details go to the OpenShift Operator Hub deployment guide for KubeTurbo