This topic describes how to increase and reduce application instances by using manual scaling. This way, you can efficiently use application resources and reduce the cost of application resources without compromising the quality of the service.
Assume that a service is added to an application and a Server Load Balancer (SLB) instance is bound to the application. When auto scaling occurs, EDAS automatically adds application instances that are scaled out to a list of backend servers and removes application instances that are scaled in from the list.
Assume that persistent storage is configured for an application. When auto scaling occurs, EDAS automatically associates application instances that are scaled out with the configured persistent storage.
- Log on to the EDAS console.
- Perform one of the following operations as needed to go to the application details
- In the left-side navigation pane, choose Container Service Kubernetes Cluster or Serverless Kubernetes Clusters page, click a cluster ID. In the Applications section of the Cluster Details page, click the name of the application for which you want to view the details. or . In the top navigation bar, select a region. In the upper part of the page, select a namespace. On the
- In the left-side navigation pane, click Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. Select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list and click the application name.
- In the upper-right corner of the Application Overview page, choose .
- In the Application Scaling dialog box, specify the total number of pods to be scaled out or scaled in for the
application and then click OK. If the number of pods is set to 0, the system physically deletes all the pods on which the application is running and retains only the basic creation information of the application.After the scaling starts, Application change in progress... appears on the Application Overview page.You can click View Details to view the detailed application change process. Wait several minutes until the application change process is complete. After the application change process is complete, view the running status of the instance in the Basic Information section of the Application Overview page. If the running status shows that a pod is running, the application is deployed.