-
Notifications
You must be signed in to change notification settings - Fork 75
Server Versions and Kubeturbo Tag Mappings
Jason Shaw edited this page Mar 8, 2024
·
66 revisions
When deploying kubeturbo, there are 2 requirements for versions:
- To allow a remote probe to connect, you need to provide the first 2 digits of the Server version number that kubeturbo will connect to. This information will be put in the configMap used by Kubeturbo to register with the Turbonomic Server
- The kubeturbo version used should always match your Turbonomic Server version. When you update the Turbonomic Server version, you should also update kubeturbo to the same version. Note that the Turbonomic Server supports N, N-1 and N+1 for kubeturbo versions, to allow for time to update. To ensure functionality, kubeturbo should be updated after the Turbonomic Server version is updated.
Examples of Turbonomic Server - Kubeturbo version matching (**NOTE: That new Turbonomic Server versions and Kubeturbo versions that are released always match). CWOM has a different version numbering, but it is based on the same Turbonomic Server version as shown below for example.
- Turbonomic Server version = 8.9.5
- CWOM Server version = 3.7.5
- Kubeturbo version = 8.9.5
- Turbonomic Server value used in
configMap
= 8.9
Note:
- You only need to specify the first 2 digits of the Turbonomic Server for the
version
in the kubeturboconfigMap
.- Minor releases within version (such as going from 8.9.1 to 8.9.5) do not require updates to the
configMap
.- Cisco provides IWO and CWOM 3.x.
- While not common, a kubeturbo version may have a dot release (8.x.y.z) to provide a hot fix, and this fix will folded into the latest version release and supported going forward on the 8.x.y versions.
For more information on What's New in both the Turbo Server and Kubeturbo refer to IBM Turbonomic Documentation, and Release Notes for more details on fixes for each version.
- For more information on Early Access features - Contact IBM Turbonomic Product Managers: [email protected] and [email protected]
Turbonomic has ended support for the Turbo 6.x (CWOM 2.3.x) versions as of August 31, 2021. Deploy the latest version of Turbo / CWOM Server, and use the corresponding KubeTurbo version.
Introduction
Kubeturbo Use Cases
Kubeturbo Deployment
Kubeturbo Config Details and Custom Configurations
Actions and how to leverage them
- Overview
-
Resizing or Vertical Scaling of Containerized Workloads
a. DeploymentConfigs with manual triggers in OpenShift Environments - Node Provision and Suspend (Cluster Scaling)
- SLO Horizontal Scaling
- Turbonomic Pod Moves (continuous rescheduling)
-
Pod move action technical details
a. Red Hat Openshift Environments
b. Pods with PVs
IBM Cloud Pak for Data & Kubeturbo:Evaluation Edition
Troubleshooting
- Startup and Connectivity Issues
- KubeTurbo Health Notification
- Logging: kubeturbo log collection and configuration options
- Startup or Validation Issues
- Stitching Issues
- Data Collection Issues
- Collect data for investigating Kubernetes deployment issue
- Changes to Cluster Role Names and Cluster Role Binding Names