Create a release order
Use a release order to publish multiple application services at the same time.
Procedure
Log on to the Container Application Service console. In the navigation pane on the left, click Application Publishing > Release Orders.
On the release and deployment dashboard, click Create Release Order.
NoteThe search box on the release and deployment dashboard page currently supports only prefix-based searches for release order names.
On the Create Release Order page, enter the following release information and click Next.
Basic information
Title: The title of the release.
Deployment unit: Displays all deployment units in the current workspace.
Application service release list: In the Available Application Services list, select the application services that you want to publish. Then, click the > icon to add them to the Selected Application Services list.
NoteIf an application service has multiple committed versions, select the version to publish. By default, the latest version is selected.
Advanced configuration
Set application service dependencies: If you select two or more application services, you can specify the dependencies between them. If there are no dependencies, you can skip this step.
You can add dependencies one by one. In the Depends On column, select the service names on which an application service depends. You can select multiple services. For example, if appservice1 depends on appservice2, select appservice2 in the Depends On column for appservice1. The same logic applies if a service depends on multiple application services.
ImportantCircular dependencies between application services are not allowed. For example, you cannot have a situation where application service A depends on application service B, and application service B also depends on application service A.
On the Preview page, confirm that the information is correct and click Create. The system automatically redirects you to the Release Order Details page. Click Publish All to start the release.
View release order details
After you create a release order, the system automatically redirects you to the Release Order Details page. On this page, you can view the execution details of the release order.
If the release order fails to initialize, you cannot proceed with the release. You can hover over Failure Reason to view the specific cause or click Re-initialize.
Pre-tasks
Execute service configuration changes: If a container service has new or modified Service configurations, a task is executed to apply these changes. Otherwise, this task is skipped.
Publish log configuration: If a log configuration is set for the container service for the first time, a pre-task is executed to create or update the log configuration. Otherwise, this task is skipped.
Application services
Application services are published in groups. The pod statuses are described as follows:
Not updated: The pod configuration is not updated to the latest version.
Updating: The pod configuration is updated to the latest version, but the pod is not yet in the ready state or has been in the ready state for less than 30 seconds.
Update successful: The pod configuration is updated to the latest version and has been in the ready state for more than 30 seconds.
Update failed: An error occurred when publishing or updating the pod.
Post-tasks
Clean up invalid service configurations: If a container service has deleted Service configurations, a task is executed to clean up the Service. Otherwise, this task is skipped.
Publish log configuration: If a log configuration is not set or is canceled for the container service, a post-task is executed to delete the log configuration. Otherwise, this task is skipped.
Post-tasks (rollback)
Roll back log configuration: If an application service needs to be rolled back to a no-resource state and its log configuration is active, a task is executed to roll back the log configuration. Otherwise, this task is skipped.
Cancel a release
After you create a release order, the system automatically redirects you to the Release Order Details page. Before the application services are published, you can click Cancel to stop the release operation.
On the Release Order Details page, click Cancel.
If the release order contains multiple applications, you can click an application service that is pending release on the right. This action opens the release page for that application. Click Cancel to cancel the release of the current application. Other applications that are not canceled can still be published.
Beta confirmation
When you configure the deployment and scheduling policies for an application service, if you enable the Beta confirmation feature, the system creates a special Beta group during the release. The system takes one machine from each deployment unit, adds it to the Beta group, and publishes this group first.
After the Beta group is published, the system automatically pauses the application release. The system owner or an O&M engineer must then confirm the release status of the application. If the application is released successfully, click Beta Confirm to continue the phased release.
If each deployment unit has only one pod, Beta confirmation has no effect.
The Beta confirmation feature is effective only when you publish a new version of an application service.
If Pause Between Groups is not selected in the grouping strategy, the remaining groups are automatically published in phases after the Beta group is published until the release is complete.
Retry and rollback
If a release fails, you can click Retry or Rollback to continue.
Retry
If you click Retry, the system continues the release.
If an application release fails, you cannot create a new release order to publish it.
Rollback
If you click Rollback, you must provide a second confirmation based on one of the following rollback scenarios:
Cancel release: No rollback version is found. Continuing the rollback stops this release.
NoteThis scenario occurs only when you try to republish the same version after a previous successful release, and the republication fails.
Roll back to no-resource state: No successful release records exist. Continuing the rollback releases all resources.
Roll back to previous version: The application is rolled back to the last successfully published version.
After the rollback is complete, click Confirm Rollback. You can click Original Application Release Details in the upper-right corner to view the details of the original release order.
If the rollback fails, you can select Retry Rollback or Cancel Rollback.
Canceling the rollback stops this release. This may result in multiple versions being online.
View pod events
During or after a release, you can view pod events to understand the scheduling and running status of the pods.
On the Release Order Details page, click a pod name to view its events.
In the pod list on the Application Service Details page, click a pod name to go to the Pod Details page. On the Pod Details page, click the Events tab to view the pod events.