The system supports application deployment based on container images, JAR packages, WAR packages, Helm packages, legacy software packages, and front-end resource packages. The configuration procedure slightly differs for these packages.
The configuration procedure slightly differs for container application deployment and host application deployment. This help document uses container application deployment as an example. You can deploy host applications by following the typical application deployment procedure.
Upload the container images and application packages to deploy to the image repository and application repository as described in "About application repository service" and "About image repository service."
Create the cloud hosts to be deployed with applications as described in " cloud hosts Configuration flowchart," and set up connections to the container clusters to be deployed with applications. The following tools must exist on the cloud hosts: systemctl and wget or curl.
To deploy specific applications or the applications to be deployed has special requirements, make sure the required tools have been installed on the cloud host. For example, a front-end resource package requires tools such as gcc, gcc-c++, pcre-devel, openssl, openssl-devel, and unzip.
To deploy and manage cloud hosts by using this system, make sure this system and the cloud hosts can reach each other.
After deploying an application on a cloud host, this system uses the public key generated upon application deployment to establish connections during the lifecycle management of applications. Therefore, do not delete or modify the public key (the /root/.ssh/authorized_keys file) generated upon application deployment on the cloud host.
To deploy an application on a container cluster or a member cluster managed by an MCP cluster, make sure the cluster has been created.
You can deploy a container image or Helm package on a container cluster or a member cluster managed by an MCP cluster. You can deploy a Jar, War package, or frontend resource package on a container cluster, a member cluster managed by an MCP cluster, or a cloud host. You can deploy a traditional image only on a cloud host.
Do not use jumbo Helm packages. Make sure a Helm package contains only services that depend on or are related to one other. As a best practice, limit the number of services to 10 or less for each Helm package.
If you deploy a Java application based on a custom image, make sure process 1 in the image is the Java program. Do not include the java –jar command in a Dockerfile to start up a JAR package. Instead, configure a script execution command in the Dockerfile to start up the JAR package.
Use JAR packages to deploy Java applications. Do not use WAR packages.