All-at-once deployment updates every instance in a Kubernetes cluster simultaneously. This is the fastest deployment mode but causes brief downtime because all instances restart at the same time. Use this mode for development, testing, or small-scale applications where short service interruption is acceptable.
For production workloads that require zero downtime, use batch release or canary release instead.
The following table compares the available deployment modes to help you choose the right one:
| Deployment mode | Downtime | Speed | Best for |
|---|---|---|---|
| All at once | Brief downtime for all instances | Fastest | Dev/test environments, simple architectures |
| Batch release | Partial capacity reduction per batch | Moderate | Production with controlled rollout |
| Canary release | None (traffic split) | Slowest | Production with traffic-based validation |
Prerequisites
Before you begin, make sure that you have:
An EDAS application deployed in a Container Service or Serverless Kubernetes Cluster
A deployment package (JAR, WAR, or image) for the new version
Access to the EDAS console
Deploy the new version
-
Log on to the EDAS console.
In the left-side navigation pane, click .
On the Applications page, select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list.
Click the name of the application to update.
In the upper-right corner of the Application Overview page, choose .
In the Release to All at Once section of the Select Deployment Mode page, click Start Deployment.
On the Release to All at Once page, configure the deployment package for the new version.
Parameter Description Application Runtime Environment Runtime environment type. Default: Standard Java Application Runtime Environment. Java Environment Java runtime for the application. Valid values: Open JDK 8, Open JDK 7, JDK 8, JDK 7, and Dragonwell 8. Current Environment Current runtime environment. Displayed only for applications deployed with JAR or WAR packages. EDAS automatically updates the Java environment or application runtime environment to the latest version. File Uploading Method How to provide the deployment package. Select Upload Package to upload a JAR or WAR file directly, or select Package Address to specify a URL. The package type must match the type used in the previous release. Supported types: JAR packages, WAR packages, and images. A JAR package is used in this example. Upload Package Available when File Uploading Method is set to Upload Package. Click Select File and choose the package to upload. Package Address Available when File Uploading Method is set to Package Address. Enter the URL of the package. For Object Storage Service (OSS) URLs with signatures, EDAS caches the file for rollbacks and scale-outs. Version Version number of the deployment package. Click Use Timestamp as Version Number to auto-generate a timestamp-based version. Time Zone Time zone for the application, specified in UTC format for the target region. (Optional) Configure advanced settings in the following sections: Scheduling Rules, Startup Command, Environment Variables, Persistent Storage, Local Storage, Application Life Cycle Management, and Log Collection Settings. For details, see the advanced settings in Use an image to deploy a Java microservices application in a Kubernetes cluster and Use a JAR or WAR package to deploy an application in an ACK cluster.
Click OK.
Verify the deployment
Go to the application details page.
In the left-side navigation pane, click Change List.
Check the Execution Status of the all-at-once release. If the status is Succeeded, the release is successful.
Related operations
To update instances in stages and reduce risk, see Batch release.
To validate a new version with a subset of traffic before full rollout, see Canary release.