Container platform actions
Turbonomic monitors the state and performance of your containerized workloads and then recommends actions to optimize these workloads.
Actions for services
Scale (through workload controllers)
Turbonomic recommends actions to scale the replicas that back the container platform services. Set the scope to the associated Workload Controller to view and execute the actions.
For details, see Workload Controller Scale Actions.
Actions for containers
Resize
Turbonomic generates container resize actions for Bare Pods where the workload has no controller.
Actions for container specs
Resize (through workload controllers)
A container spec retains the historical utilization data of ephemeral containers. Turbonomic uses this data to make resize decisions that assure optimal utilization of resources. By default, all replicas of the same container for the same workload type resize consistently.
For details, see Workload Controller Resize Actions.
Actions for container pods
-
Move
Move a pod that is controlled by a ReplicationController, ReplicaSet, or Deployment (through a ReplicaSet) to another node (VM) to address performance issues or improve infrastructure efficiency. For example, if a particular node is congested for CPU, you can move pods to a node with sufficient capacity. If a node is underutilized and is a candidate for suspension, you must first move the pods before you can safely suspend the node.
For details, see Container Pod Move Actions.
-
Provision or suspend
When recommending node provision or suspend actions, Turbonomic will also recommend provisioning pods (based on demand from DaemonSets) or suspending the related pods.
For details, see Container Pod Provision and Suspension Actions.
Actions for workload controllers
-
Resize
Actions associated with a workload controller resize container specs vertically to assure optimal utilization of resources. This is a natural representation of these actions because the parent controller's container specs for vCPU limits/requests and vMem limits/requests are modified. The workload controller then rolls out the changes in the running environment.
For details, see Workload Controller Resize Actions.
Resize actions for certain types of workloads may be blocked or set to recommend-only, which means that they are currently not executable in Turbonomic. These actions usually require a dependent action or an external configuration to be completed first. For more information, see this topic.
-
Scale
Actions associated with a workload controller scale replicas horizontally to maintain Service Level Objectives (SLOs) for your applications. This is a natural representation of these actions because the parent controller's number of replicas are modified. The workload controller then rolls out the changes in the running environment.
For details, see Workload Controller Scale Actions.
Actions for namespaces
Resize quota
Turbonomic treats quotas defined in a namespace as constraints when making resize decisions. If existing actions would exceed the namespace quotas, Turbonomic recommends actions to resize up the affected namespace quota.
Note that Turbonomic does not recommend actions to resize down a namespace quota. Such an action reduces the capacity that is already allocated to an application. The decision to resize down a namespace quota should include the application owner.
For details, see Namespace Actions.
Actions for container platform clusters
None
Turbonomic does not recommend actions for a container platform cluster. Instead, it recommends actions for the containers, pods, nodes (VMs), and volumes in the cluster. Turbonomic shows all of these actions when you scope to a container platform cluster and view the Pending Actions chart.
Actions for nodes (VMs)
A node (cloud or on-prem) is represented as a Virtual Machine entity in the supply chain.
For nodes in the public cloud, Turbonomic reports the cost savings or investments attached to these actions.
For details, see Node Actions.