An existing cluster is required. If you do not have an existing cluster, refer to Create a cluster on how to create one.
Log on to the Container Service console.
Click Applications in the left navigation pane and click Create Application in the upper-right corner.
Enter the application information, and click Create with Orchestration Template.
- Name: The name of the application to be created. In this example, the application name is wordpress-test.
- Version: The version of the application to be created. By default, the version is 1.0.
- Cluster: The cluster which the application will be deployed to.
- Update Method: The release method pf the application. You can select Standard Release or Blue-Green Release. Refer to Instructions on Release Strategies.
- Description: Information of the application. This information will be displayed in the Application List page.
- Pull Docker Image: When selected, Container Service pulls the latest Docker image in the registry to create the application, even when the tag of the image does not change.
In order to improve efficiency, Container Service caches the image; and at deployment, if the tag of the image is consistent with that of the local cache, Container Service uses the cached image instead of pulling the image from the registry. Therefore, if you modify your code and image but do not modify the image tag, Container Service will use the old image cached locally to deploy the application. When this option is selected, Container Service ignores the cached image and re-pulls the image from the registry no matter whether the tage of the image is consistent with that of the cached image, ensuring that the latest image and code are always used.
Click Use Existing Application Template, and click Select beside the wordpress template.
Modify corresponding settings in the template edit box.
You can make modifications in the template, or select the service that you want to modify and click Edit to modify the configurations.
aliyun.routing.port_80: http://wordpressindicates that requests from
http://wordpress.$testDomainare forwarded to Port 80 on the container after the container starts running.
Click Create and deploy.
Click View Application List, Back to Application List or Applications in the left navigation pane, and click wordpress-test to view the application details.
Click the service name web to view the service details.
Click the access endpoint address of the service web. This address is the domain name for access.
The WordPress page is displayed.
- The domain name in all preceding examples is only used for testing. You must replace it with your own domain name.
- If you cannot access the endpoint address, refer to Access link troubleshooting.