This topic describes how to create a batch release in the console. This feature enables you to release different versions of an application easily and iterate applications rapidly.

Background information

Note In Kubernetes clusters of the latest version, alicloud-application-controller is installed by default. This component is only available in Kubernetes 1.9.3 and later versions. You can upgrade your cluster through the console.

Procedure

  1. Log on to the Container Service console.
  2. In the left-side navigation pane, choose Applications > Releases to go to the Releases page.
  3. Click the Batch Release tab and click Create Batch Release in the upper-right corner.
    Note If the button is dimmed, it indicates that you need to upgrade your cluster first.
  4. On the Batch Release Basic Information tab, specify the following parameters: application name, cluster name, namespace, and release option. Click Next.
    Batch release configuration
  5. On the Batch Release Configuration tab, configure the Pods and Service, and then click Update to create an application.
    Update configuration
  6. Go to the Releases page and click the Batch Release tab. You can find the newly created application and its status is Not Started. Click View Details in the Actions column.
    Release details
  7. On the Details tab, you can find more information about the application. Click Change Configuration in the upper-right corner to change the application configuration.
  8. On the page that appears, change the configuration and then click Update.
    Change configuration
  9. You are redirected to the Releases page by default. Click the Batch Release tab and you can find the current status of the application. After the first batch is deployed, click View Details.
    Details page
  10. Click the Details tab. You can see that two Pods are listed in the Not Started list and two Pods are listed in the Completed list. This indicates that the first batch has been released. Click Continue to release the second batch of Pods. Click Roll Back to roll back to the previous version.
    Rollback
  11. After the release is completed, click the History tab and you can choose to roll back to a history version.
    Roll back to a history version

What to do next

You can create a batch release to quickly verify the functionalities of a new application version while serving all production traffic. A batch release requires less resources than a blue-green release. Currently, you can only create batch releases through the wizard. Support for YAML configuration files will be available soon.