Creating a Workload

• Cloud Container Engine (CCE): a highly reliable and high-performance service that allows enterprises to manage containerized applications. With support for Kubernetes-native applications and tools, CCE makes it simple to set up an environment for running containers in the cloud.
• Elastic Cloud Server (ECS): a scalable and on-demand cloud server. It helps you to efficiently set up reliable, secure, flexible application environments, ensuring stable service running and improving O&M efficiency.
• Virtual Private Cloud (VPC): an isolated, private virtual network environment that you apply for in the cloud. You can configure the IP address ranges, subnets, and security groups, as well as assign elastic IP addresses and allocate bandwidth in a VPC.

• A cluster is a collection of computing resources, including a group of nodes. A container runs on a node. Before creating a containerized application, you must have an available cluster.
• A node is a virtual or physical machine that provides computing resources. You must have sufficient node resources to ensure successful operations such as creating applications.
• A workload indicates a group of pods running on CCE. CCE supports third-party application hosting and provides the full lifecycle (from deployment to O&M) management for applications. This section describes how to use a container image to create a workload.

1. Prepare the environment as described in Table 1.

   Table 1 Preparing the environment

   No.	Category	Procedure
   1	Creating a VPC	Create a VPC before you create a cluster. A VPC provides an isolated, configurable, manageable virtual network environment for CCE clusters. If you already have a VPC, skip to the next task. Log in to the management console. In the service list, choose Networking > Virtual Private Cloud. On the Overview page, click Create VPC. Follow the instructions to create a VPC. Retain default settings for parameters unless otherwise specified.
   2	Creating a key pair	Create a key pair before you create a containerized application. Key pairs are used for identity authentication during remote login to a node. If you already have a key pair, skip this task. Log in to the management console. In the service list, choose Data Encryption Workshop. In the navigation pane, choose Key Pair Service. Go to the Private Key Pairs tab. Then, click Create Key Pair. Enter a key pair name, confirm I agree to host the private key of the key pair. and I have read and agree to the Key Pair Service Disclaimer., and click OK. View and save the private key. For security purposes, a key pair can be downloaded only once. Keep it secure to ensure successful login.

2. Create a cluster and a node.
   1. Log in to the CCE console. On the Clusters page, click Buy Cluster and select the type for the cluster to be created.

      Configure cluster parameters and select the VPC created in 1.

   2. Buy a node and select the key pair created in 1 as the login option.

3. Deploy a workload on CCE.
   1. Log in to the CCE console and click the name of the cluster to access the cluster console. In the navigation pane, choose Workloads and click Create Workload.
   2. Configure the following parameters, and retain the default settings for other parameters:
      • Workload Name: Set it to apptest.
      • Pods: Set it to 1.
   3. In the Container Settings area, select the image uploaded in Building and Uploading an Image.
   4. In the Container Settings area, choose Environment Variables and add environment variables for interconnecting with the MySQL database. The environment variables are set in the startup script.
      Note

      In this example, interconnection with the MySQL database is implemented through configuring the environment variables. Determine whether to use environment variables based on your service requirements.

      Table 2 Configuring environment variables

      Variable Name	Variable Value/Variable Reference
      MYSQL_DB	Database name.
      MYSQL_URL	IP address and port number of the database.
      MYSQL_USER	Database username.
      MYSQL_PASSWORD	Database user password.

   5. In the Container Settings area, choose Data Storage and configure cloud storage for persistent data storage.
      Note

      In this example, the MongoDB database is used and persistent data storage is also needed, so you need to configure cloud storage. Determine whether to use cloud storage based on your service requirements.

      The mount path must be the same as the MongoDB storage path in the Docker startup script. For details, see the startup script. In this example, the path is /usr/local/mongodb/data.

   6. In the Service Settings area, click to add a Service, configure the Service parameters, and click OK.
      Note

      In this example, the application can be accessed from the Internet through an EIP.

      • Service Name: name of the application that can be accessed externally. In this example, this parameter is set to apptest.
      • Service Type: Select NodePort.
      • Service Affinity
        • Cluster-level: This Service-associated workload is accessible via the node IP address and port of any cluster node. Cross-node access incurs route redirection overhead and obscures the client source IP address.
        • Node-level: This Service-associated workload is accessible only via the node IP address and port of the hosting node. Direct access eliminates route redirection overhead and preserves the client source IP address.
      • Port
        • Protocol: Set it to TCP.
        • Service Port: port for accessing the Service.
        • Container Port: port that the application will listen on the container. In this example, this parameter is set to 8080.
        • Node Port: Set it to Auto. The system automatically opens a real port on all nodes in the current cluster and then maps the port number to the Service port.
   7. Click Create Workload.

      After the workload is created, you can view the running workload in the workload list.

After a workload is created, you can access the workload to check whether the workload has been deployed.

In the preceding configuration, a NodePort Service is configured for the workload. This means that you can access the workload using <node-IP-address>:port. If the workload can be accessed properly, it has been deployed.

You can obtain the access address from the Access Mode tab on the workload details page.