Create WordPress with an orchestration template

Last Updated: Nov 28, 2017

Prerequisite

If you have not created a cluster before, create a cluster first. For information about how to create a cluster, see Create a cluster.

Procedure

  1. Log on to the Container Service console.

  2. Click Applications in the left-side navigation pane, and click Create Application in the upper-right corner.

    1

  3. Complete the following configurations for the application you are about to create and then click Create with Orchestration Template.

    1

    • Name: Enter the name of the application. Enter wordpress-test in this example.
    • Version: Enter the version of the application. By default, 1.0 is entered.
    • Cluster: Select the cluster on which the application will be deployed.
    • Update: The update method of the application. Select Standard Release or Blue-Green Release. For details, see Introductions on release strategies.
    • Description: Enter the information of the application. The entered description will be displayed on the Application List page.
    • Pull Docker Image: With this check box selected, Container Service pulls the latest Docker 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 check box selected, Container Service ignores the cached image and re-pulls the image from the repository when deploying the application to ensure the latest image and codes are always used.
  4. Click Use Existing Orchestration Template, and click Select next to the wordpress template.

    1

  5. Modify the corresponding configurations by making modifications in the template directly or clicking Edit to edit the services.

    aliyun.routing.port_80: http://wordpress indicates that requests from http://wordpress.$testDomain are forwarded to port 80 on the container after the container is successfully run.

  6. Click Create and Deploy.

  7. A page indicating the application is created appears. Click View Application List or Back to Application List on the page or click Applications in the left-side navigation pane. Click the application name wordpress-test to view the application details.

    1

  8. Click the service name web under Services to view the service details.

    1

  9. Click the access endpoint, the domain name for access, of the service web.

    1

    The WordPress page is displayed.

    9

Note:

  • The domain name in this example is only used for test. Bind your own domain name.
  • If you cannot access the endpoint, see Access link troubleshooting.
Thank you! We've received your feedback.