A containerized application is created using either a component template or an application template.
Name of the component template you will use.
A component name must:
Affinity: Affinity rules define in which AZs the application will be deployed. It is recommended that the AZs in which cluster nodes will be deployed should be selected as affinity AZs.
AntiAffinity: Anti-affinity rules define in which AZs the application must not be deployed.
If the affinity or anti-affinity rule is inappropriate, the CCE console displays a Warning dialog box "According to the selected affinity or anti-affinity rule, the application may not be scheduled onto any node. Are you sure you want to continue?" Click Cancel and correct the affinity or anti-affinity rule.
Node on which the component will run.
Number of instances that the component has. Every instance is shipped as a container.
A service name must:
Indicates whether the component is accessible to external networks.
If Yes is selected, the following parameters are displayed:
Indicates whether the component uses a NodePort or LoadBalancer.
If no load balancer is available for selection, return to the ELB console to create a new load balancer. For details, see (Optional) Creating a Load Balancer. After a new load balancer is created, it is displayed in the Load Balancer drop-down list.
Network protocol to be used by the component.
Listening port to be used by the component.
Mandatory if Service Type is set to LoadBalancer.
This parameter indicates the port used by the chosen load balancer to provide services externally. The port number ranges from 1 to 65535 (inclusive).
Mandatory if Service Type is set to NodePort.
If Service Type is set to LoadBalancer, the node port must be different from the ports used by all the listeners of the ELB instance, to avoid the application creation failure caused by port conflicts.
Application templates are created using the graphic App Designer.
If a containerized application is created from an application template, the application must be deployed on a container cluster in which all nodes have a public IP address. Otherwise, the application will be inaccessible to users.
The App Designer page then appears, displaying information about the created containerized application.
After the application is successfully created, you can access it from a browser.
To obtain the application's service address, perform the following steps: