All Products
Search
Document Center

Container Service for Kubernetes:Cost optimization check

Last Updated:Dec 01, 2025

The cost management suite of Container Service for Kubernetes (ACK) provides the cost optimization check feature. You can use this feature to identify idle resources in your cluster. After idle resources are identified, you can manage the resources based on your business requirements. This feature also checks whether workload resource configurations are reasonable and provides recommended configurations.

Cost optimization check items

Idle resource check

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

Abnormal conditions

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 instance is attached to cluster resource tags but does not belong to any resource object in this 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.

Workload resource configuration check

Checks whether memory and CPU request values or limit values are set for workloads.

Resource type

Abnormal conditions

Workloads

  • No memory request value or limit value is set for the workload.

  • No CPU request value or limit value is set for the workload.

Prerequisites

The cost optimization check feature is available only for ACK managed clusters and ACK dedicated clusters. Make sure 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 (discontinued).

Perform a cost optimization check

Note

When you perform a cost optimization check, the system initiates a cluster inspection in your cluster. You can also view the cost optimization check results on the Cluster Inspections page.

  1. Log on to the ACK console. In the left navigation pane, click Clusters.

  2. On the Clusters page, find the cluster you want and click its name. In the left-side pane, choose Cost Suite > Cost Optimization.

  3. On the Cost Optimization page, click the Cost Optimization Check tab, and then click Check.

View cost optimization check results

On the Cost Optimization page, click the Cost Optimization Check tab to view the results of the most recent check.

  • In the Idle Resource Optimization check results, click Handle in the Actions column of a specific resource to go to the corresponding console to manage the idle resource.

  • In the Improper Workload Resource Configuration Optimization check results, click Recommended Resource Configuration in the Actions column of a specific workload to go to the Resource Profiling page of the workload. You can upgrade or downgrade the specifications based on the analysis results on the Resource Profile page. For more information, see Resource profiling.

You can also click Historical Checks on the Cost Optimization Check page to view historical check results and take actions based on the results.