Deploying an Nginx Workload in a CCE Autopilot Cluster

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Workloads. In the upper right corner, click Create Workload.
3. Configure the basic information about the workload.

   In this example, only some mandatory parameters are described. You can keep the default values for other parameters. For details about the parameters, see Creating a Workload. You can select a reference document based on the workload type.

   

   Parameter	Example Value	Description
   Workload Type	Deployment	A workload defines the creation, status, and lifecycle of pods. By creating a workload, you can manage and control the behavior of multiple pods, such as scaling, updating, and restoration. Deployment: runs a stateless application. It supports online deployment, rolling upgrade, replica creation, and restoration. StatefulSet: runs a stateful application. Each pod for running the application has an independent state. Job: a one-off job. After the job is complete, the pods are automatically deleted. CronJob: a time-based job runs a specified job in a specified period. For more information about workloads, see Workload Overview. Nginx is mainly used to forward requests, balance loads, and distribute static content. You do not need to store any Nginx persistent data locally. Therefore, Nginx is deployed as a Deployment in this example.
   Workload Name	nginx	Enter a name for the workload.
   Namespace	default	A namespace is a conceptual grouping of resources or objects. Each namespace provides isolation for data from other namespaces. After a cluster is created, the default namespace is created by default. If there is no special requirement, select default.
   Pods	1	Enter the number of pods.

4. Configure the containers.

   In this example, only some mandatory parameters are described. You can keep the default values for other parameters. For details about the parameters, see Creating a Workload. You can select a reference document based on the workload type.

   

   Parameter	Example Value	Description
   Image Name	nginx	Click Select Image. In the displayed dialog box, click the Open Source Images tab and select a public image.
   Image Tag	latest	Select the required image tag.
   CPU Quota	0.25 cores	Specify the CPU limit, which defines the maximum number of CPU cores that can be used by a container. The default value is 0.25 cores.
   Memory Quota	512 MiB	Specify the memory limit, which is the maximum memory available for a container. The default value is 512 MiB. If the memory exceeds 512 MiB, the container will be terminated.

5. Specify the Service settings.

   Click the plus sign (+) under Service Settings. The Create Service page is displayed.

   In this example, external access to Nginx is required. So you need to create a Service of the LoadBalancer type.

   In this example, only some mandatory parameters are described. You can keep the default values for other parameters. For details about the parameters, see Service . Select a reference document based on the Service type.

   

   Parameter	Example Value	Description
   Service Name	nginx	Enter a name for the Service.
   Service Type	LoadBalancer	Select a Service type, which determines how the workload is accessed. ClusterIP: The workload can only be accessed using IP addresses in the cluster. LoadBalancer: The workload can be accessed from the public network through a load balancer. For more information about the Service types, see Service.
   Load Balancer	Dedicated Network (TCP/UDP) & Application (HTTP/HTTPS) Use existing elb-nginx	Select Use existing if there is a load balancer available. NOTE: You can only select a dedicated load balancer that is in the same VPC as the cluster and handles network traffic. If there is no available load balancer, select Auto create to create one with an EIP bound. For details, see Creating a LoadBalancer Service.
   Ports	Protocol: TCP	Protocol: Select a protocol for the load balancer listener.
   	Container Port: 80	Container Port: Enter the port on which the application listens. This port must be the same as the listening port provided by the application for external systems. If the nginx image is used, set this port to 80.
   	Service Port: 8080	Service Port: Enter a custom port. The load balancer will use this port as the listening port to provide an entry for external traffic.

6. Click Create Workload.

   After the Deployment is created, it is in the Running state in the Deployment list.

   

7. Obtain the external access address of Nginx.

   Click the name (nginx) of the workload to go to its details page. On the Access Mode tab, view the access address in the format of {EIP bound to the load balancer}:{Access port}.

   

8. In the address box of your browser, enter {EIP bound to the load balancer}:{Access port} to access the application.

   

Command line operations are required. You can perform related operations in either of the following ways:

• Perform operations using CloudShell. You need to ensure kubectl has been configured in CloudShell and the cluster has been connected using CloudShell. For details, see Connecting to a Cluster Using CloudShell.
• Perform operations on the ECS that is in the same VPC as the cluster and with an EIP bound. For details, see Purchasing and Using a Linux ECS. You also need to install kubectl and connect to the cluster through kubectl.

The following uses the first method as an example to describe how you can use kubectl to create an Nginx workload.

1. Click the cluster name to access the cluster console.
2. In the upper right corner, click Kubectl CloudShell to access CloudShell.
   

   Using CloudShell to connect to a cluster is only available in some regions. For details, see the management console.

   

3. Create a YAML file for creating a workload. In this example, the file name is nginx-deployment.yaml. You can change it as needed.

   vim nginx-deployment.yaml

   The file content is as follows:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: nginx     # Workload name
   spec:
     replicas: 1     # Number of pods
     selector:
       matchLabels:  # Selector for selecting resources with specific labels
         app: nginx  
     template:
       metadata:
         labels:     # Labels
           app: nginx
       spec:
         containers:
         - image: nginx:latest   # {Image name}:{Image tag}
           name: nginx
         imagePullSecrets:
         - name: default-secret

   Press Esc to exit editing mode and enter :wq to save the file.

4. Run the following command to create the workload:

   kubectl create -f nginx-deployment.yaml

   If information similar to the following is displayed, the workload is being created:

   deployment.apps/nginx created

5. Run the following command to check the workload status:

   kubectl get deployment

   If the value of READY is 1/1, the pod created for the workload is available. This means the workload has been created.

   NAME     READY   UP-TO-DATE   AVAILABLE   AGE
   nginx    1/1     1            1           4m59s

   The following table describes the parameters in the command output.

   Parameter	Example Value	Description
   NAME	nginx	Workload name.
   READY	1/1	The number of available pods/desired pods for the workload.
   UP-TO-DATE	1	The number of pods that have been updated for the workload.
   AVAILABLE	1	The number of pods available for the workload.
   AGE	4m59s	How long the workload has run.

6. Create a Service of the LoadBalancer type for the workload.

   An existing load balancer is used to create the Service.To automatically create a load balancer, see Using kubectl to Create a Load Balancer.

   Create a YAML file for creating the Service. In this example, the file name is nginx-elb-svc.yaml. You can change it as needed.

   vim nginx-elb-svc.yaml

   The file content is as follows:

   apiVersion: v1 
   kind: Service 
   metadata: 
     name: nginx      # Service name
     annotations:
       kubernetes.io/elb.id: <your_elb_id>          # Load balancer ID. Replace it with the actual value.
       kubernetes.io/elb.class: performance         # Load balancer type
   spec:
     selector: 
        app: nginx
     ports: 
     - name: service0 
       port: 8080     
       protocol: TCP 
       targetPort: 80  
     type: LoadBalancer

   Press Esc to exit editing mode and enter :wq to save the file.

   Parameter	Example Value	Description
   kubernetes.io/elb.id	405ef586-0397-45c3-bfc4-xxx	ID of an existing load balancer. NOTE: You can only select a dedicated load balancer that is in the same VPC as the cluster and handles network traffic. In the navigation pane of the network console, choose Elastic Load Balance > Load Balancers. Locate the load balancer. The ID is displayed below the name.
   kubernetes.io/elb.class	performance	Load balancer type. The value can only be performance, which means that only dedicated load balancers are supported.
   selector	app: nginx	Selector, which is used by the Service to send traffic to pods with specific labels. NOTICE: The value must be the same as that of matchLabels in the YAML file for creating the workload. In this example, the value is app: nginx.
   ports.port	8080	The port used by the load balancer as an entry for external traffic. You can use any port.
   ports.protocol	TCP	Protocol for the load balancer listener.
   ports.targetPort	80	Port used by a Service to access the target container. This port is closely related to the applications running in the container. If the nginx image is used, set this port to 80.

7. Run the following command to create a Service:

   kubectl create -f nginx-elb-svc.yaml

   If information similar to the following is displayed, the Service has been created:

   service/nginx created

8. Run the following command to check the Service:

   kubectl get svc

   If information similar to the following is displayed, the workload access mode has been configured:

   NAME         TYPE           CLUSTER-IP     EXTERNAL-IP                  PORT(S)          AGE
   kubernetes   ClusterIP      10.247.0.1     <none>                       443/TCP          18h
   nginx        LoadBalancer   10.247.56.18   xx.xx.xx.xx,xx.xx.xx.xx      8080:30581/TCP   5m8s

9. In the address box of your browser, enter {External access address}:{Service port} to access the workload. The external access address is the first IP address displayed for EXTERNAL-IP, and the Service port is 8080.