You can use Alibaba Cloud Container Service for Kubernetes to release application versions in batches, achieving fast version verification and rapid iteration of applications.

Background information

Note The latest Kubernetes cluster has installed alicloud-application-controller by default. For older versions of clusters, only versions of 1.9.3 and later are currently supported, and you can upgrade old versions of clusters through the prompt link on the console.

Procedure

  1. Log on to the Container Service console.
  2. Under Kubernetes, click Application > Release in the left-side navigation pane. Click Create batch release in the upper-right corner.
    Note If the button is gray, you can upgrade the cluster by following the upgrade link.


  3. Configure batch release information, including the application name, cluster, namespace, and options. Click Next.


  4. On the batch publishing configuration page, configure the backend pod and service, and then click Update to create an application.


  5. Return to the release list, an application is displayed in the Not started status. Click Detail on the right.


  6. On the application detail page, you can view more information. Click Change Configuration in the upper-right corner of the page to make a batch release change.


  7. Configure changes for the new version of the application, and then click Update.


  8. By default, you return to the release list page, where you can view the batch release status of the application. After completing the first deployment, click Detail.


  9. You can see that the Not Started list is has two pods and the Completed list has two pods, which indicates that the first batch has been completed in batch release. Click Continue，you can release the second batch of pods. Click Roll Back to roll back to the previous version.


  10. When completing the release, click Historyto roll back to history versions.


What to do next

You can use batch release to quickly verify your application version without traffic consumption. Batch release is more resource-saving than blue-green release. Currently, batch release can be performed on only web pages. The yaml file editing is to be opened later to support more complex operations.