edit-icon download-icon

Change application configurations

Last Updated: Feb 11, 2018

You can update the application configurations in the Container Service console.

Procedure

  1. Log on to the Container Service console.

  2. Click Applications in the left-side navigation pane.

  3. Select the cluster where the application you want to change configurations resides from the Cluster list.

  4. Click Update at the right of the application you want to change configurations.

    1

  5. The Change Configuration dialog box appears. Modify the configurations.

    1

    Note: You must update the Version. Otherwise, the OK button is unavailable.

    • Use Latest Image: With this switch turned on, Container Service pulls the latest image from the repository to deploy the application, even when the image tag does not change.

      To improve efficiency, Container Service caches the image. When deploying an application, Container Service uses the cached image instead of pulling the image from the repository if the image tag is the same as that of the local cache. Therefore, if you modify your codes and image but do not modify the image tag for the convenience of upper business, Container Service will use the old image cached locally to deploy the application. With this switch turned on, Container Service ignores the cached image and re-pulls the image from the repository when deploying the application to make sure the latest image and codes are always used.

    • Force Reschedule: By default, to avoid losing the container data in the local data volume on the current machine, Container Service restarts the container or recreates a container on the current machine when you change the application configurations. To schedule the container to another machine, turn on the Force Reschedule switch. Then, Container Service schedules the container to another machine according to your scheduling settings in the Template. For more information, see FAQs about changing application configurations.

      Note: After scheduling the container to another machine by turning on the Force Reschedule switch, the container data in the local data volume on the former machine are lost. So proceed with caution.

    • Release Mode: The update method of the application. Select Standard Release or Blue-Green Release. For more information, see Overview of release policies.

    • Use Existing Orchestration Template: Click Use Existing Orchestration Template to select a template to change the application configurations. A confirmation dialog box appears. Click Confirm.

      Note: The new template will overwrite the current template.

  6. Click OK in the Change Configuration dialog box.

Subsequent operation

If the application is not updated after you change the configurations, you can redeploy the application to apply the configuration modifications. For more information, see Redeploy an application.

Thank you! We've received your feedback.