Turbonomic Actions
Last updated
Last updated
This feature is in beta. Please read the documentation carefully.
The IBM Turbonomic Action Center offers multiple types of actions destined to improve the overall performance of your cluster(s). The integration between Kubecost and Turbonomic allows you to view the estimated savings incurred by executing these actions.
To be able to see the savings cards, you must first enable the Turbonomic Integration. This is required for Kubecost to be able to pull action data from your Turbonomic client.
The Resize Workload Controllers page shows workloads which would benefit from changes to their resource requests, as recommended by Turbonomic. The Current and Predicted cost columns are calculated using the Spec Cost Prediction API: the Current column is calculated by inferring the CPU and/or memory requests on all Containers in the workload, while the Predicted column is calculated by using the new request values recommended by Turbonomic for each container. Please note that at the moment, this functionality is only available for Deployments and StatefulSets.
The Suspend Container Pods page shows pods that Turbonomic recommends to be suspended. The Current cost column represents the monthly rate for the Pod in question, queried over a period of 7d offset 48h to account for reconciliation. The Predicted cost column is zero for suspension actions.
The Suspend Virtual Machines page shows virtual machines (nodes) that Turbonomic recommends to be suspended. The Current cost column represents the monthly rate for the node in question, queried over a period of 7d offset 48h to account for reconciliation. The Predicted cost column is zero for suspension actions.
The Move Container Pods page shows pods that Turbonomic recommends to be moved from one node to another. The Current cost column represents the monthly rate for the destination node, queried over a period of 7d offset 48h to account for reconciliation. The Efficiency column contains a hyperlink to the Efficiency page for the destination node, highlighting the infrastructure idle corresponding to it.
