how to use the idle resource optimization feature to identify idle resources in a cluster - Container Service for Kubernetes

The cost management suite of Container Service for Kubernetes (ACK) provides the idle resource optimization feature. You can use the idle resource optimization feature to identify idle resources in your cluster. After idle resources are identified, you can manage the resources based on your business requirements. This topic describes how to use the idle resource optimization feature to identify idle resources in a cluster.

Prerequisites

Only ACK managed clusters and ACK dedicated clusters support idle resource optimization. Ensure that an ACK managed cluster or an ACK dedicated cluster is created. For more information, see Create an ACK managed cluster or Create an ACK dedicated cluster.

Perform an idle resource check

Important

When you perform an idle resource check, the system scans all resources in your cluster and retrieves the resource status. Idle resource checks may interrupt the applications in your cluster. We recommend that you perform idle resource checks during off-peak hours.

Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of the cluster that you want to manage and choose Cost Suite > Cost Optimization in the left-side navigation pane.
On the Cost Optimization page, click the Idle Resource Optimization tab. Then, click Check below Reports.
In the Note dialog box, read the information and select I have read and understand the information. Then, click OK.

Check items

The idle resource optimization feature checks whether the following resources are idle: Elastic Compute Service (ECS) instances, Elastic Block Storage (EBS) devices, Classic Load Balancer (CLB) instances, and elastic IP addresses (EIPs).

Resource type	Condition
ECS instance	The Elastic Compute Service (ECS) instance has a label of the cluster but does not belong to the cluster.
EBS device	The Elastic Block Storage (EBS) device is not attached to any node in the cluster. The node to which the EBS device is attached is idle. The EBS device has a label of the cluster but is not attached to any resource in the cluster.
CLB instance	The Classic Load Balancer (CLB) instance is in the Stopped state. No backend server is associated with the CLB instance. The total sum of the weights of all backend servers associated with the CLB instance is 0. No listener is configured for the CLB instance. All listeners of the CLB instance are in the Stopped state.
EIP	The node to which the elastic IP address (EIP) is associated is idle. The Server Load Balancer (SLB) instance to which the EIP is associated is idle. The EIP is not associated with any resources.

View the check results

Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of the cluster that you want to manage and choose Cost Suite > Cost Optimization in the left-side navigation pane.
On the Cost Optimization page, click the Idle Resource Optimization tab to view the check results.
- In the Last Check Result section, you can check whether idle resources are identified in the last check.
- In the Reports list, find the report for the check you performed and click View Details in the Actions column to go to the Idle Resource Details page. On the Idle Resource Details page, select an instance ID and click Handle to go to the corresponding console.
  Note
  If no idle resource is identified in the check, View Details is dimmed in the Actions column.