This topic describes how to manually increase or reduce the number of application instances for an application. This way, you can efficiently use application resources and reduce the cost of application resources without compromising the service quality.
Background information
You may configure a Service for an application and bind a Server Load Balancer (SLB) instance to the application. In this case, if scaling occurs, EDAS automatically adds or removes application instances that are involved in scaling to or from the list of backend servers of the SLB instance.
You may configure persistent storage for an application. In this case, if scaling occurs, EDAS automatically associates application instances that are added with the configured persistent storage.
Procedure
- Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications. In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace. From the Cluster Type drop-down list, select Kubernetes Cluster. Then, find the application that you want to manage and click the name in the Application Name column.
- In the upper-right corner of the Application Overview page, choose .
- In the Application Scaling dialog box, specify the expected total number of pods 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 status of the instance in the Basic Information section of the Application Overview page. If the status shows that a pod is running, the application is deployed.
