Container platform actions

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.

Resize

Turbonomic generates container resize actions for Bare Pods where the workload has no controller.

• 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.

  Note:

  Move actions for certain types of pods may be blocked or set to recommend-only, which means that they are currently not executable in Turbonomic. For details, see Special cases for 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 sctions.

• 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 in the Deployment are modified. The workload controller then rolls out the changes in the running environment.

  For more information, see Workload controller resize actions.

  Note:

  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 example, a workload controller resize up action may be temporarily blocked if there is insufficient resources in the corresponding node or namespace. In this case, a node provision or namespace quota resize action must be completed first.

  For more information, see Special cases for workload controller resize actions.

• 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 in the Deployment are modified. The workload controller then rolls out the changes in the running environment.

  For details, see Workload controller scale actions.

• Move

  Move a resource, such as a container pod, to another node (virtual machine) 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. When a move is completed, the underlying resource entity in Red Hat OpenShift Virtualization is moved, not the workload controller that represents the resource.

  Note: Turbonomic respects any affinity or anti-affinity rule configurations for Red Hat OpenShift Virtualization virtual machines. For more information about affinity and anti-affinity rules, see Pod affinity and anti-affinity rules.

• CPU memory resize

  Resize actions for a Red Hat OpenShift Virtualization workload controller (virtual machine) resize the container specs to assure optimal utilization of resources. The workload controller then rolls out the changes in the running environment.

  Note:

  • Turbonomic prevents resizes below resource requirements. For instance, if a VM on operating system A has a configuration within Red Hat OpenShift Virtualization that defines the minimum resources required for that VM to run, such as 2 VCPUs and 2 GiB of memory, Turbonomic reads these requirements and takes them into consideration when generating resize actions. This consideration ensures that Turbonomic does not resize the VM below the minimum resource requirements.
  • Turbonomic does not resize VMs that are configured using instance types.

For actions that are associated with Red Hat OpenShift Virtualization virtual machines pods, Turbonomic takes into consideration any run strategy that is defined in the virtual machine spec (RunStrategy field). For instance, if a run strategy is defined so that a virtual machine runs only once, Turbonomic does not recommend resize actions for that virtual machine. For move actions, Turbonomic can change the run strategy to generate a disruptive resize action for the move. After the resize is completed, the run strategy is reset.

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.