Container Service for Kubernetes:Enable CPU Suppress

Billing

No fee is charged when you install or use the ack-koordinator component. However, fees may be charged in the following scenarios:

• ack-koordinator is a non-managed component that occupies worker node resources after it is installed. You can specify the amount of resources requested by each module when you install the component.

• By default, ack-koordinator exposes the monitoring metrics of features such as resource profiling and fine-grained scheduling as Prometheus metrics. If you enable Prometheus metrics for ack-koordinator and use Managed Service for Prometheus, these metrics are considered custom metrics and fees are charged for these metrics. The fee depends on factors such as the size of your cluster and the number of applications. Before you enable Prometheus metrics, we recommend that you read the Billing topic of Managed Service for Prometheus to learn about the free quota and billing rules of custom metrics. For more information about how to monitor and manage resource usage, see Query the amount of observable data and bills.

Procedure

You can enable the CPU Suppress feature at the cluster level through a ConfigMap. Additionally, you can configure related parameters in the ConfigMap, such as the CPU utilization threshold of the node (cpuSuppressThresholdPercent) with CPU Suppress enabled, to achieve fine-grained resource management.

1. Create a file named configmap.yaml based on the following ConfigMap content:

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: ack-slo-config
     namespace: kube-system
   data:
     # Enable CPU Suppress.
     resource-threshold-config: |
       {
         "clusterStrategy": {
           "enable": true
         }
       }

2. Check whether the ack-slo-config ConfigMap exists in the kube-system namespace.

   • If the ack-slo-config ConfigMap exists, we recommend that you use the PATCH method to update the ConfigMap. This method does not change other settings in the ConfigMap.

     kubectl patch cm -n kube-system ack-slo-config --patch "$(cat configmap.yaml)"

   • If the ack-slo-config ConfigMap does not exist, run the following command to create a ConfigMap named ack-slo-config:

     kubectl apply -f configmap.yaml

3. Run the following command to query the CPU cores that are allocated to the BE pods on the node:

   cat /sys/fs/cgroup/cpuset/kubepods.slice/kubepods-besteffort.slice/cpuset.cpus

   Expected output:

   10-25,35-51,62-77,87-103

   The expected output shows that the following CPU cores are allocated to the BE pods on the node: 10-25,35-51,62-77,87-103. This indicates that the available CPU resources for BE pods are restricted after enabling CPU Suppress, based on current resource usage.

4. Optional: Configure advanced parameters based on the following ConfigMap content.

   CPU Suppress allows you to further configure the CPU utilization threshold.

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: ack-slo-config
     namespace: kube-system
   data:
     resource-threshold-config: |
       {
         "clusterStrategy": {
           "enable": true,
           "cpuSuppressThresholdPercent": 65
         }
       }

   The following table describes the key parameters:

   Parameter	Type	Value range	Description
   enable	Boolean	true false	true: enables CPU Suppress. false: disables CPU Suppress.
   cpuSuppressThresholdPercent	Integer	[0, 100]	The CPU utilization threshold of the node. Default value: 65. Unit: %.