Workload controller

A workload controller is a container platform entity that watches the state of your pods and then requests changes where needed. Examples of workload controllers are Deployments and StatefulSets. A single workload controller can contain one or more container spec entities, and it can be related to one or more running replica pods. Like container specs, workload controllers are persistent.

You can execute actions to resize container specs or scale replicas when you set the scope to a workload controller.

Synopsis

Workload controller in the supply chain
Synopsis
Provides: N/A
Consumes: N/A
Discovered through: Kubeturbo agent that you deployed to your cluster

Monitored resources

Turbonomic monitors quotas (limits and requests) for VCPU and VMem, and associates how much each workload controller is contributing to a quota based on all replicas. This allows Turbonomic to generate rightsizing decisions, and manage the quota as a constraint to rightsizing. Metrics on resource consumption are shown in the Container Spec, Container, and Container Pod views.

Workload controller actions

Turbonomic supports the following actions:

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