Manual scaling lets you set the exact number of running pods for an application deployed on a Kubernetes cluster in Enterprise Distributed Application Service (EDAS). Use it to match capacity to traffic changes or scheduled events, and to control resource costs without compromising service quality.
How it works
During scaling, EDAS automatically updates related infrastructure:
| Component | Behavior during scaling |
|---|---|
| Load balancer | If a Service is configured and a Server Load Balancer (SLB) instance is bound, EDAS adds or removes scaled pods from the SLB backend server list. |
| Persistent storage | If persistent storage is configured, EDAS associates newly added pods with the existing persistent storage. |
Prerequisites
Before you begin, make sure that you have:
An EDAS account with access to the EDAS console
An application deployed on a Kubernetes cluster in EDAS
Scale an application
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.
Find your application and click its name in the Application Name column.
In the upper-right corner of the Application Overview page, choose Scale > Manual Scaling.
In the Application Scaling dialog box, specify the expected total number of pods and click OK.
Setting the pod count to 0 physically deletes all running pods for the application. Only the basic creation information of the application is retained.
Verify scaling status
After scaling starts, Application change in progress... appears on the Application Overview page. Click View Details to monitor the change process.
When the change completes, check the Basic Information section of the Application Overview page. If the pod status shows as running, the scaling is complete.
