Publishing an Application by Rolling Update


Rolling Update is a deployment mode for application publishing (replacing old pods with new ones gradually), while continuing to serve clients without incurring downtime.


You need to maintain only 1 cluster if Rolling Update is used. The pods of the cluster can deploy new versions of the application independently. Different from the Blue-Green Deployment, the Rolling Update deploys applications smoothly.


For more information about Rolling Update, see Zero-downtime Deployment in Kubernetes.

Prerequisites

Organization and namespace name are selected.

Creating a Publish Form

  1. In the EnOS Management Console, navigate to Enterprise Container Platform and select Publish > Rolling Update.
  2. Click New Publish Form to complete the configuration information. According to the selected Deployment, the system will filter the Service, Route and Service Monitor of the same name to update synchronously.


The steps to publish an app via Rolling Update in Container Cluster Management are similar to those in Developer Studio. For more information, see Publishing an Application by Rolling Update.

Checking the Publish Result

When the publishing starts, the status of the publish form is changed to Running. You can check the running status and result of the publish form in the Publish Logs section.

Next Step

When the publishing is completed, if it is successful, you can click Close in the Publish Operations section to close the publish form. If you need to roll back to the previous version of the application, click Rollback, and the system will start the operation immediately.


If the publishing fails, you can click Start in the Publish Operations section to publish again, or click Rollback, and the system will roll back to the previous version of the application.