Skip to content
Eva Tuczai edited this page Mar 14, 2024 · 50 revisions

IBM Turbonomic with KubeTurbo

Unified Control of Kubernetes and Red Hat OpenShift Services, Workloads, Platform and Infrastructure

License

Kubeturbo leverages IBM Turbonomic's patented analysis engine to provide visibility and control across the entire stack in order to assure the performance of running micro-services in Kubernetes Pods, as well as the efficiency of underlying infrastructure.

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

What's New

NOTE: All Kubeturbo deployment related documentation is now in the official IBM Docs here. Portion of this GitHub wiki related to Deployment and Configuration is not being updated, please refer to the official IBM Docs going forward. Portions related to use cases are still here.


In 8.10.6 we will block execution of resize actions of workloads that are operator controlled by leveraging auto-created groups of Container Specs discovered with an operator owner reference. For users that have an ORM, which will allow these resize actions to occur, you can exclude your workloads from this group. Additionally workloads that are part of System namespaces, such as kube-system or openshift-* will be automatically excluded from generating resizing actions. To modify these configurations, see the wiki page here

In 8.10.5, in collaboration with Cloud Pak for Data, we have introduce a special packaging of Turbonomic for CP4D customers. Learn more here.

In 8.10.4 we are happy to announce support for Service Level Objective (SLO) Based horizontal scaling actions for Dynatrace as the APM source of data. This release introduces support for SLO based horizontal scaling actions for Dynatrace to maintain SLOs for your applications that are hosted in Kubernetes clusters. With these actions, you can scale the replicas that are horizontally scalable Kubernetes Services. For details on how to set up this target type, see Dynatrace in the IBM Turbonomic docs.

In 8.10.3, IBM Cloud Red Hat OpenShift Clusters when deployed in Azure via IBM Cloud Satellite now support stitching in Turbonomic where you will see the Red Hat OpenShift Node stitched to the Azure VM and infrastructure supporting the cluster. For more information on enabling this support go to the IBM Docs here

Check out the details for the latest kubeturbo updates here in IBM Turbonomic Documentation, and Release Notes for more details on fixes for each version.. For IBM Turbonomic Server and product updates with release notes, go here.

  • SLO based control ). Read the blog here
  • Manage horizontal scaling of services without thresholds
  • Manage the trade-offs of performance, availability of resources, and compliance
  • Leverage your SLO data to add response time and throughput leveraging telemetry data collected - Istio, Prometheus, Instana and now Dynatrace!
  • Be more sustainable

We have made improvements in versions 8.3.5-8.3.3 in the following use cases:

  • Node Pool/Group and OCP MachineSets Turbonomic will visualize Node pool/groups and OpenShift machine sets for clusters, and when we horizontally scale a public cloud based node pool, you can also see a summary of cost investment and savings associated with managing cluster capacity
  • StatefulSet Resizing Turbonomic will allow a user to execute a resize on a stateful set type in a running environment. Previously the action was automatically failed. These actions can still be integrated with a pipeline.

With the release of 8.3.1, we are pleased to announce

  • CPU Throttling Turbonomic can now recommend increasing vCPU limit capacity to address slow response times associated with CPU throttling. As throttling drops and performance improves, it analyzes throttling data holistically to ensure that a subsequent action to decrease capacity will not result in throttling.
  • Power10 Support KubeTurbo now supports Kubernetes clusters that run on Linux ppc64le (including Power10) architectures. Select the architecture you want from:
    • Docker Hub for KubeTurbo version 8.3.1 to 8.7.4 (docker.io/turbonomic/kubeturbo:<version>)
    • IBM Container Registry for Kubeturbo 8.7.5 and higher (icr.io/cpopen/turbonomic/kubeturbo:<version>)

To deploy Kubeturbo via Operator, refer to Kubeturbo via OpenShift Operator Hub or Kubeturbo Manual Operator Method

Refer to the official IBM Docs here for the current information

Kubeturbo

Introduction
  1. What's new
  2. Supported Platforms
Kubeturbo Use Cases
  1. Overview
  2. Getting Started
  3. Full Stack Management
  4. Optimized Vertical Scaling
  5. Effective Cluster Management
  6. Intelligent SLO Scaling
  7. Proactive Rescheduling
  8. Better Cost Management
  9. GitOps Integration
  10. Observability and Reporting
Kubeturbo Deployment
  1. Deployment Options Overview
  2. Prerequisites
  3. Turbonomic Server Credentials
  4. Deployment by Helm Chart
    a. Updating Kubeturbo image
  5. Deployment by Yaml
    a. Updating Kubeturbo image
  6. Deployment by Operator
    a. Updating Kubeturbo image
  7. Deployment by Red Hat OpenShift OperatorHub
    a. Updating Kubeturbo image
Kubeturbo Config Details and Custom Configurations
  1. Turbonomic Server Credentials
  2. Working with a Private Repo
  3. Node Roles: Control Suspend and HA Placement
  4. CPU Frequency Getter Job Details
  5. Logging
  6. Actions and Special Cases
Actions and how to leverage them
  1. Overview
  2. Resizing or Vertical Scaling of Containerized Workloads
    a. DeploymentConfigs with manual triggers in OpenShift Environments
  3. Node Provision and Suspend (Cluster Scaling)
  4. SLO Horizontal Scaling
  5. Turbonomic Pod Moves (continuous rescheduling)
  6. Pod move action technical details
    a. Red Hat Openshift Environments
    b. Pods with PVs
IBM Cloud Pak for Data & Kubeturbo:Evaluation Edition
Troubleshooting
  1. Startup and Connectivity Issues
  2. KubeTurbo Health Notification
  3. Logging: kubeturbo log collection and configuration options
  4. Startup or Validation Issues
  5. Stitching Issues
  6. Data Collection Issues
  7. Collect data for investigating Kubernetes deployment issue
  8. Changes to Cluster Role Names and Cluster Role Binding Names
Kubeturbo and Server version mapping
  1. Turbonomic - Kubeturbo version mappings
Clone this wiki locally