Publish now

更新时间:
复制 MD 格式

After you create an application service, you can publish it from the LHC console.

You can publish an application service in one of the following two ways:

Prerequisites

Before you publish an application service, ensure that the cluster has sufficient node resources, such as CPU and memory. Otherwise, pods cannot be scheduled to nodes.

Method 1: Publish immediately after creating the application service

  1. After creating the application service, click Publish Now. For more information, see Create an application service.

  2. On the Deployment Details page, click Publish All.

    Note

    The application service is published when its status changes to Published.

Method 2: Publish from the application service details page

  1. Log on to the LHC console.

  2. In the navigation pane on the left, click Publish O&M > Application Service.

  3. On the application service list page, click the name of an application service to go to the Application Service Details page.

  4. In the upper-right corner, click Publish.

    Note
    • If the application service has multiple versions, a message prompts you to confirm whether to publish the latest version of the container service.

    • To publish a previous version, click the Versions tab, and then click Publish to the right of the version.

  5. On the Publish Preview page, verify the information, and then click Start Publish.

  6. After the deployment is created, on the Deployment Details page, click Publish All.

    Note

    The application service is published when its status changes to Published.

What to do next

View deployment details

After you click Publish, you are automatically redirected to the Deployment Details page. You can expand Deployment Tasks on the right to view the detailed deployment status.

Retry rollback

If a deployment fails, click Retry to continue the deployment, or click Rollback to restore the last successfully published version.

Note

You can roll back an application only if it has other successfully published deployment packages besides the current version. If there are no successful deployment records, a rollback releases all resources.