Pulling an Image to Deploy an Application in a CCE Cluster

Configure the parameters shown in the table and keep the default settings for other parameters.

In the Service Settings area, click the plus sign (+) and create a Service for external network access to the workload. This example shows how to create a LoadBalancer Service. Configure the below parameters in the sliding window on the right.

Wait until the workload is created. The created workload in the Running state will be displayed on the Deployments tab.

Figure 1 Workload created

You can check whether kubectl has been installed by running kubectl version. If kubectl has been installed, you can skip this step.

The Linux environment is used as an example to describe how to install and configure kubectl. For more installation methods, see kubectl.

1. Download kubectl.

   cd /home
   curl -LO https://dl.k8s.io/release/{v1.29.0}/bin/linux/amd64/kubectl

   {v1.29.0} specifies the version. You can replace it as required.

2. Install kubectl.

   chmod +x kubectl
   mv -f kubectl /usr/local/bin

1. Log in to the CCE console and click the cluster name to access the cluster console. Choose Overview in the navigation pane.
2. On the page displayed, locate the Connection Information area, click Configure next to kubectl, and view the kubectl connection information.
3. In the window that slides out from the right, locate the Download the kubeconfig file area, select Intranet access for Current data, and download the corresponding configuration file.
4. Log in to the VM where the kubectl client has been installed and copy and paste the configuration file (for example, kubeconfig.yaml) downloaded in the previous step to the /home directory.
5. Save the kubectl authentication file to the configuration file in the $HOME/.kube directory.

   cd /home
   mkdir -p $HOME/.kube
   mv -f kubeconfig.yaml $HOME/.kube/config

6. Run the kubectl command to see whether the cluster can be accessed.

   For example, to view the cluster information, run the following command:

   kubectl cluster-info

   Information similar to the following is displayed:

   Kubernetes master is running at https://*.*.*.*:5443
   CoreDNS is running at https://*.*.*.*:5443/api/v1/namespaces/kube-system/services/coredns:dns/proxy
   To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

vi nginx-deployment.yaml

The file content is as follows:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - image: nginx:alpine
        name: nginx
      imagePullSecrets:
      - name: default-secret

kubectl create -f nginx-deployment.yaml

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

deployment "nginx" created

kubectl get deployment

If information similar to what is shown here is displayed, the workload has been created:

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

The parameters in the command output are described as follows:

• NAME: specifies the name of a workload.
• READY: indicates the number of available pods/expected pods for the workload.
• UP-TO-DATE: specifies the number of pods that have been updated for the workload.
• AVAILABLE: specifies the number of pods available for the workload.
• AGE: specifies how long the workload has run.

vi nginx-elb-svc.yaml

apiVersion: v1 
kind: Service 
metadata: 
  annotations:   
    kubernetes.io/elb.class: union
    kubernetes.io/elb.autocreate: 
        '{
            "type": "public",
            "bandwidth_name": "cce-bandwidth",
            "bandwidth_chargemode": "bandwidth",
            "bandwidth_size": 5,
            "bandwidth_sharetype": "PER",
            "eip_type": "5_bgp"
        }'
  labels:
    app: nginx
  name: nginx 
spec: 
  ports: 
  - name: service0 
    port: 8080
    protocol: TCP 
    targetPort: 80
  selector: 
    app: nginx 
  type: LoadBalancer

kubectl create -f nginx-elb-svc.yaml

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

service/nginx created

kubectl get svc

If information similar to the following is displayed, the access type has been configured, and the workload is accessible:

NAME         TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)          AGE
kubernetes   ClusterIP      10.247.0.1       <none>          443/TCP          3d
nginx        LoadBalancer   10.247.130.196   **.**.**.**   8080:31540/TCP   51s