Container pod provision and suspension actions
When recommending node provision or suspend actions, Turbonomic will also recommend provisioning pods (based on demand from DaemonSets) or suspending the related pods.
Pod provision action in response to node provision
When recommending node provision actions, Turbonomic also recommends pod provision actions that reflect the projected demand from required DaemonSet pods, and respects the maximum number of pods allowed for a node. This ensures that any application workload can be placed on the new node and stay within the desired range of vMem/vCPU usage, vMem/vCPU request, and number of consumers.
The action details for a pod provision action shows the related node that you need to provision. Click the node name to set it at your scope.

Turbonomic treats static pods as DaemonSets for the purpose of provisioning nodes. Because a static pod provides a node with a specific capability, it is controlled by the node and is not accessible through the API server. If a node to be provisioned requires a static pod, Turbonomic generates actions to provision the node and the corresponding static pod.
Turbonomic creates an auto-generated group of static pods when it
discovers a static pod on each node in a cluster. To view all the auto-generated groups, go
to Search, select Groups, and then type mirror pods
as your search
keyword.

Pod suspension action in response to node suspension
When recommending node suspension actions, Turbonomic also recommends suspending the DaemonSet pods that are no longer required to run the suspended nodes.
The action details for a pod suspension action shows the related node that you need to suspend. Click the node name to set it at your scope.

Turbonomic treats static pods as DaemonSets for the purpose of suspending nodes. Because a static pod provides a node with a specific capability, it is controlled by the node and is not accessible through the API server. If the only workload type on a node is a static pod, Turbonomic generates actions to suspend the node and the corresponding static pod.
Turbonomic creates an auto-generated group of static pods when it
discovers a static pod on each node in a cluster. To view all the auto-generated groups, go
to Search, select Groups, and then type mirror pods
as your search
keyword.
