A release order lets you publish multiple application services simultaneously. This topic describes how to create a release order to publish application services and view its details.
Create a release order
Log on to the LHC console.
In the navigation pane on the left, click Publishing and O&M > Release Orders.
On the release and deployment dashboard, click Create Release Order.
NoteThe search box on the release and deployment dashboard supports only prefix-based searches for release order titles.
On the Create Release Order page, enter the following release information and click Next.
Basic Information
Title: Enter a title for the release.
Type: The release type. Supported types include Phased Release, Blue-Green Deployment (Ingress Application), Blue-Green Deployment (Deployment Unit Dimension), and End-to-end Canary Release. In this example, Phased Release is selected. For more information about blue-green deployments, see Blue-green deployment. For more information about end-to-end canary releases, see End-to-end canary release.
Namespace: Select the namespace where the application service to be published is located.
Application Service Release List: In the Available Application Services list, click the application services that you want to add to the Selected Application Services list.
NoteIf an application service has multiple committed versions, select the version to publish. The latest version is selected by default.
Publish to Specified Deployment Units: This feature is disabled by default. If you enable this feature, select the required deployment units. The application service is published only to the selected deployment units that are in the current version's configuration. No changes are made to existing pods in unselected deployment units.
WarningThis feature is intended for data center disaster recovery scenarios. You can select specific deployment units to ensure that application services are published normally during disaster recovery. For more information about disaster recovery, see Multi-cluster federated release for disaster recovery.
Advanced Configuration
Set application service dependencies: When you select two or more application services, you can configure their dependencies. If the application services have no dependencies, you can skip this step. In the Depends on column for a service, you can enter the name of the service that it depends on. You can specify multiple dependencies for a single service. For example, if appservice1 depends on appservice2, you can enter appservice2 in the Depends on column for appservice1.
ImportantCircular dependencies between application services are not allowed. A circular dependency occurs when Application Service A depends on Application Service B, and Application Service B in turn depends on Application Service A.
On the Preview page, confirm that the information is correct and click Create. You are automatically redirected to the Release Order Details page. Click Publish All to start the release.
View release order details
After a release order is created, you are automatically redirected to the Release Order Details page. On this page, you can view the execution details of the release order.
If a release order fails to initialize, it cannot be published. You can hover over Failure Reason to view the cause or click Re-initialize.
In the lower-left corner of the details page, click View Operation Logs to view the event types, operators, and operation times for the release order.
Prerequisites
Execute service configuration changes: If a Service configuration is added to or modified for the container service, a task to change the Service configuration is executed. Otherwise, this task is skipped.
Publish log configuration: If you are configuring a log configuration for the container service for the first time, a pre-release task is executed to create or update the log configuration. Otherwise, this task is skipped.
Application services
When you publish an application service by group, 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 ready 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 while publishing or updating the pod.
Post-release tasks
Clean up invalid service configurations: If a Service configuration for the container service is deleted, a task to clean up the Service is executed. Otherwise, this task is skipped.
Publish log configuration: If no log configuration is specified for the container service or if the existing log configuration is canceled, a post-release task is executed to delete the log configuration. Otherwise, this task is skipped.
Post-release tasks (rollback)
Revert log configuration: If the application service needs to be reverted to a state with no resources and the log configuration for the application service has already taken effect, a task to revert the log configuration is executed. Otherwise, this task is skipped.
Cancel a release
After a release order is created, you are automatically redirected to the Release Order Details page. Before the application service is published, you can click Cancel to stop the release.
On the Release Order Details page, click Cancel.
If the release order contains multiple applications, you can click an application on the right to go to its release page. On that page, click Cancel to cancel the release of only that application. The other applications in the release order 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. The system adds one server from each deployment unit to the Beta group and publishes this group first.
After the Beta group is published, the system automatically pauses the application release. The owner or an O&M engineer must confirm the release status of the application. If the application is released normally, click Beta Confirm to continue the phased release.
If each deployment unit has only one pod, Beta confirmation is not applicable.
The Beta confirmation feature takes effect only when a new version of an application service is published.
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.
Retry and rollback
If a release fails, you can click Retry or Rollback to proceed.
Retry
If you click Retry, the system continues the release.
If an application release fails, you cannot create a new release order to publish that application.
Rollback
If you click Rollback, you must confirm the operation. The confirmation prompt varies based on the rollback scenario:
Cancel release: No version is available for rollback. If you continue, the rollback operation stops this release.
NoteThis scenario occurs only when a version was successfully published once, but a re-release of the same version fails.
Revert to no-resource state: No successful release records exist. If you continue, the rollback operation 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 the current release. This may result in multiple versions being online at the same time.
View pod events
During or after a release, you can view pod events to check the scheduling and running status of pods.
On the Release Order Details page, click a pod name to view its events.
On the Application Service Details page, in the pod list, click a pod name to go to the Pod Details page. Click the Events tab to view the pod events.