Configure scheduled resource scaling in ASK Knative

Procedure

1. Configure a scheduled resource scaling policy.
   You can use a ConfigMap to configure a scheduled resource scaling policy. Each Knative service is bound to one policy. The following code block shows a configuration example:

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: cron-autoscaler
     namespace: default
   data:
     jobs:
      - name: "workday"
        schedule: "* * 1-5"
        timeseries:
        - timeSlice: 01:30:30
          replicas: 1
        - timeSlice: 05:30:30
          replicas: 2
        - timeSlice: 07:30:30
          replicas: 5
        - timeSlice: 10:24:30
          replicas: 8
        - timeSlice: 11:47:30
          replicas: 10
        - timeSlice: 13:17:30
          replicas: 6
        - timeSlice: 16:50:30
          replicas: 9
        - timeSlice: 20:17:30
          replicas: 5
        - timeSlice: 23:30:30
          replicas: 1
      - name: "holiday"
        schedule: "* * 0,6"
        timeseries:
        - timeSlice: 08:24:30
          replicas: 4
        - timeSlice: 11:47:30
          replicas: 3
        - timeSlice: 13:17:30
          replicas: 2

   • In the schedule field, the first number indicates the day of a month. The second number indicates the month of a year. The rest indicates the days of a week. In the preceding example, 1-5 indicates Monday to Friday, and 0,6 indicates Saturday and Sunday.
   • timeseries: specifies the numbers of instances at the specified time points. The time points are specified in the 24-hour notation in the Hour:Minute:Second format.

   Note

   • Policy updates apply to all Knative services that are bound to the policy.
   • If you delete the policy, the change does not apply to the Knative services that are bound the policy. The Knative services do not scale resources to zero.
2. Use the scheduled resource scaling policy.
   After you configure a scheduled resource scaling policy, you can apply the policy to Knative services.

   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: helloworld-go-ppa
     annotations:
       alicloud.autoscaling.service.knative.dev/timeseries: "cron-autoscaler"
   spec:
     template:
       metadata:
         labels:
           app: helloworld-go-ppa
         annotations:
           autoscaling.knative.dev/class: "ppa.autoscaling.knative.dev"
           alicloud.autoscaling.knative.dev/metric-target: "cpu:50"
       spec:
         containers:
           - image: registry.cn-hangzhou.aliyuncs.com/knative-samples/helloworld-go:160e4dc8
             resources:
               requests:
                 cpu: '200m'              

   • Specify the policy name by using alicloud.autoscaling.service.knative.dev/timeseries.
   • Specify the scheduled scaling plug-in by using autoscaling.knative.dev/class: "ppa.autoscaling.knative.dev".
   • Specify multiple Horizontal Pod Autoscaler (HPA) metrics. The Knative community version allows you to specify only one HPA metric. In ASK Knative, you can specify multiple HPA metrics by using alicloud.autoscaling.knative.dev/metric-target. For example, you can specify the number of CPU cores and memory by setting the parameter to cpu:50,memory:50.
   • Set autoscaling.knative.dev/minScale to the minimum number of a resource.
   • Set autoscaling.knative.dev/maxScale to the maximum number of a resource.

   Note The following formulas are used to determine the maximum or minimum number of a resource after HPA scaling:

   • Minimum number of a resource after HPA scaling = min(autoscaling.knative.dev/minScale,Number of a resource specified in the scheduled scaling policy)
   • Maximum number of a resource after HPA scaling = max(autoscaling.knative.dev/maxScale,Number of a resource specified in the scheduled scaling policy)

Verify the result

Check the changes in the number of a resource after you apply the scheduled scaling policy. The following trend chart shows an example.