Implement autoscaling with Alibaba Cloud metrics

apiVersion: apps/v1 
kind: Deployment
metadata:
  name: nginx-deployment-basic
  labels:
    app: nginx
spec:
  replicas: 2
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.7.9 
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginx
  namespace: default
spec:
  ports:
    - port: 80
      protocol: TCP
      targetPort: 80
  selector:
    app: nginx
  type: ClusterIP

1. In the left-side navigation pane, choose Marketplace > Orchestration Templates.
2. On the Templates page, select HPA and click Create Application to deploy the following YAML file.

   apiVersion: autoscaling/v2beta2
   kind: HorizontalPodAutoscaler
   metadata:
     name: ingress-hpa
   spec:
     scaleTargetRef:
       apiVersion: apps/v1
       kind: Deployment
       name: nginx-deployment-basic
     minReplicas: 2
     maxReplicas: 10
     metrics:
       - type: External
         external:
           metric:
             name: sls_ingress_qps
             selector:
               matchLabels:
                 sls.project: "***"
                 sls.logstore: "nginx-ingress"
                 sls.ingress.route: "default-nginx-80"
           target:
             type: AverageValue
             averageValue: 10
       - type: External
         external:
           metric:
             name: sls_ingress_latency_p9999
             selector:
               matchLabels:
                 # default ingress log project is k8s-log-clusterId
                 sls.project: "***"
                 # default ingress logstre is nginx-ingress
                 sls.logstore: "nginx-ingress"
                 # namespace-svc-port
                 sls.ingress.route: "default-nginx-80"
                 # sls vpc endpoint, default true
                 # sls.internal.endpoint:ture
           target:
             type: Value
             # sls_ingress_latency_p9999 > 10ms
             value: 10

   The following table lists the HPA parameters that are used in the preceding example.

   Parameter	Description
   sls.ingress.route	-
   sls.logstore	-
   sls.project	-
   sls.internal.endpoint	Whether the project has an internal endpoint. Default is true.

   Note

   This topic uses the sls_ingress_qps and sls_ingress_latency_p9999 metrics to implement autoscaling. Each metric has a different type of target.

   • The target of sls_ingress_qps is AverageValue, indicating that the request rate is an average value among pods.
   • The target of sls_ingress_latency_p9999 is Value, indicating that the latency is a total value.

   These two types are commonly used in HPA configurations.
3. On the Templates - HPA page, click Create.

#! /bin/bash
## Use Apache Benchmark to send requests to the application exposed by the ingress. The test lasts 300 seconds and sends 10 concurrent requests per second.
ab -t 300 -c 10 <The domain of the ingress>

1. In the left-side navigation pane, choose Clusters. On the Clusters page, find the target cluster and click Manage in the Actions column.
2. At the top of the page, click Open Cloud Shell.
3. Run the kubectl describe hpa ingress-hpa command to check the scaling status.