Scaling a Workload

After scaling policies are defined, pods can be automatically added or deleted based on resource changes, fixed time, and fixed periods. You do not need to manually adjust resource allocation to cope with service changes and data traffic spikes.

• Auto scaling: You can set metric-based, scheduled, and periodic policies. After configuration, pods can be automatically added or deleted based on resource changes or the specified schedule.
• Manual scaling: Pods are immediately added or deleted after the configuration is complete.

Scaling policy priority: If you do not manually adjust the number of pods, auto scaling policies will take effect for resource scheduling. If manual scaling is triggered, auto scaling policies will be temporarily invalid.

• Metric-based policy: Supports auto scaling of a workload based on the CPU/memory usage.
  1. Log in to the CCE console. In the navigation pane, choose Workloads > Deployments or StatefulSets. In the same row as the target workload, choose More > Scaling.
  2. In the Auto Scaling area, click Add Scaling Policy.
  3. Set the policy parameters as listed in Table 1.

     Table 1 Parameters for adding a metric-based policy

     Parameter	Description
     Policy Name	Enter the name of the scaling policy. The policy name must be 1 to 64 characters in length and start with a letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.
     Policy Type	Set this parameter to Metric-based policy. The alarm policy is triggered based on historical data. The system checks whether the indicators set by the user in the monitoring window meet the triggering conditions every minute. If the triggering conditions are met for N consecutive periods, the system performs the action specified by the policy.
     Metric	Set the metrics that describe the resource performance data or status. CPU Usage: CPU usage of the measured object. The value is the percentage of the used CPU cores to the total CPU cores. Physical Memory Usage: percentage of the physical memory size used by the measured object to the physical memory size that the measured object has applied for.
     Trigger Condition	The value can be higher (>) or lower (<) than a threshold. When the usage of the preceding metrics reaches the specified value, the scaling policy is triggered. For example, if Metric is set to CPU Usage and this parameter is set to > 70%, the scaling policy is triggered when the CPU usage exceeds 70%.
     Monitoring window	Size of the data aggregation window. If the value is set to 60, metric statistics are collected every 60 seconds.
     Threshold Crossings	Number of consecutive times that the threshold is reached within the monitoring window. The calculation cycle is fixed at one minute. If the parameter is set to 3, the action is triggered if threshold is reached for three consecutive measurement periods.
     Action	Action executed after a policy is triggered. Two actions are available: add or reduce pods.

  4. Click OK.
  5. In the Auto Scaling area, check that the policy has been started.
     Figure 1 Viewing a metric-based policy
     

     When the trigger condition is met, the auto scaling policy starts automatically.

• Scheduled policy: scaling at a specified time.
  1. In the Auto Scaling area, click Add Scaling Policy. Select Scheduled policy.
     Figure 2 Scheduled Policy
     

     Table 2 Parameters for adding a scheduled policy

     Parameter	Description
     Policy Name	Enter the name of the scaling policy. The policy name must be 1 to 64 characters in length and start with a letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.
     Policy Type	Set this parameter to Scheduled policy.
     Trigger Time	Time at which the policy is enforced.
     Action	Action executed after a policy is triggered. Three actions are available: add pods, reduce pods, and set the number of pods.

  2. Click OK.
  3. In the Auto Scaling area, check that the policy has been started.
     Figure 3 Viewing a scheduled policy
     
     When the trigger time is reached, you can see on the Pods tab page that the auto scaling policy has taken effect.

     Figure 4 Auto scaling having taken effect
     
• Periodic policy: scaling at a specified time on a daily, weekly, or monthly basis.
  1. In the Auto Scaling area, click Add Scaling Policy. Select Periodic policy.
     Figure 5 Periodic policy
     

     Table 3 Parameters for adding a periodic policy

     Parameter	Description
     Policy Name	Enter the name of the scaling policy. The policy name must be 1 to 64 characters in length and start with a letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.
     Policy Type	Set this parameter to Periodic policy.
     Time Range	Specify the time for triggering the policy.
     Action	Action executed after a policy is triggered. Three actions are available: add pods, reduce pods, and set the number of pods.

  2. Click OK.
  3. In the Auto Scaling area, check that the policy has been started.
     Figure 6 Viewing a periodic policy
     

     When the trigger condition is met, the auto scaling policy starts automatically.