Skip to content

Component resource elastic scaling

Users can control the Control Plane Components realizes the elastic scaling policy. Currently, it provides three elastic scaling methods: metric shrinking (HPA), timing shrinking (CronHPA), and vertical scaling (VPA). Users can choose the appropriate elastic scaling policy according to their needs. The following uses index scaling (HPA) as an example to introduce the method of creating an auto scaling policy.

Prerequisites

Make sure the helm app Metrics Server is installed on the cluster, refer to Install metrics-server plugin

create policy

Take the istiod of the dedicated cluster as an example, the specific operation is as follows:

  1. Select the corresponding cluster in [Container Management], and click to enter Workload -> Stateless Load page to find istiod ;

  2. Click the workload name to enter the Auto Scaling tab page;

  3. Click the Edit button to configure the auto scaling policy parameters;

    • Policy name: Enter the name of the auto scaling policy. Please note that the name can contain up to 63 characters, and can only contain lowercase letters, numbers, and separators ("-"), and must start and end with lowercase letters or numbers, such as hpa -my-dep .
    • Namespace: The namespace where the payload resides.
    • Workload: The workload object that performs auto scaling.
    • Target CPU Utilization: The CPU usage of the Pod under the workload resource. The calculation method is: the request (request) value of all Pod resources/workloads under the workload. When the actual CPU usage is greater/lower than the target value, the system automatically reduces/increases the number of Pod replicas.
    • Target Memory Usage: The memory usage of the Pod under the workload resource. When the actual memory usage is greater/lower than the target value, the system automatically reduces/increases the number of Pod replicas.
    • Replica range: the elastic scaling range of the number of Pod replicas. The default interval is 1 - 10.

  4. Click OK to finish editing, and the new policy has taken effect.

More elastic scaling configurations

Please refer to:

Comments