Container Service for Kubernetes:Deploy workloads and configure load balancing in ACK managed clusters (Auto Mode)

Prerequisites

Before you begin, ensure that you have:

• An ACK managed cluster (Auto Mode). See Create an ACK managed cluster.

• kubectl connected to the cluster. See Connect to a cluster.

Step 1: Create a namespace

Create a dedicated namespace to keep the sample resources isolated from other workloads in the cluster.

1. Log on to the ACK console. In the left navigation pane, click Clusters.

2. On the Clusters page, click the name of the target cluster. In the left navigation pane, click Namespaces and Quotas.

3. Click Create. In the dialog box, enter a namespace name (this tutorial uses my-nginx-namespace), configure other settings as needed, and click OK.

Step 2: Deploy the NGINX application and create a Service

Deploy an NGINX Deployment named my-nginx with two replicas and a ClusterIP Service named my-nginx-svc to expose it within the cluster.

• Deployment: 2 replicas, NGINX container image, port 80.

• Service: ClusterIP type, routes port 80 to the container's port 80, selected by the app: nginx label.

For more details on creating workloads and Services, see Deploy a workload and Service management.

1. Create my-nginx.yaml with the following content:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: my-nginx    # The name of the sample application.
     namespace: my-nginx-namespace  # Replace with the name of the namespace you created.
     labels:
       app: nginx
   spec:
     replicas: 2       # The number of replicated pods.
     selector:
       matchLabels:
         app: nginx     # Must match the selector in the Service.
     template:
       metadata:
         labels:
           app: nginx
       spec:
       #  nodeSelector:
       #    env: test-team
         containers:
         - name: nginx
           image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
           ports:
           - containerPort: 80         # Must be exposed in the Service.
   ---
   apiVersion: v1
   kind: Service
   metadata:
     labels:
       app: nginx
     name: my-nginx-svc
     namespace: my-nginx-namespace  # Replace with the name of the namespace you created.
   spec:
     ports:
     - port: 80
       protocol: TCP
       targetPort: 80
     selector:
       app: nginx
     type: ClusterIP   # If Flannel is used, change this to NodePort.

2. Apply the manifest:

   kubectl apply -f my-nginx.yaml

3. Verify the Deployment and Service are running:

   • Check the Deployment:

     kubectl get deployment my-nginx -n my-nginx-namespace

     Expected output:

     NAME       READY   UP-TO-DATE   AVAILABLE   AGE
     my-nginx   2/2     2            2           4m36s

   • Check the Service:

     kubectl get svc my-nginx-svc -n my-nginx-namespace

     Expected output:

     NAME           TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
     my-nginx-svc   ClusterIP   192.XX.XX.164     <none>        80/TCP    42s

Step 3: Create an ALB Ingress and its associated resources

ALB Ingress routes external traffic to applications inside the cluster. It requires three resources working together:

Before creating an ALB Ingress, review its concepts and requirements. See ALB Ingress management.

Step 4: Verify the deployment

Before accessing the application, confirm that all layers are healthy.

1. Check that all pods are running:

   kubectl get pods -n my-nginx-namespace

   Expected output (all pods in Running state):

   NAME                        READY   STATUS    RESTARTS   AGE
   my-nginx-XXXXXXXXX-XXXXX    1/1     Running   0          5m
   my-nginx-XXXXXXXXX-XXXXX    1/1     Running   0          5m

2. Check that the Ingress has an endpoint:

   If ADDRESS is empty, wait another minute and retry. ALB provisioning typically takes about 1 minute.

   kubectl get ingress my-albingress -n my-nginx-namespace

   Expected output (the ADDRESS field shows the ALB DNS name):

   NAME             CLASS   HOSTS   ADDRESS                                       PORTS   AGE
   my-albingress    alb     *       alb-******.<regionID>.alb.aliyuncs.com        80      2m

3. Paste the ALB DNS name into a browser. The NGINX welcome page confirms the deployment is successful.

   

Troubleshooting

If the application is not accessible, use the following commands to diagnose the issue.

(Optional) Step 5: Clean up resources

To delete all resources created in this tutorial, run the following commands. Replace resource names with your actual names if different.

kubectl delete deployment my-nginx -n my-nginx-namespace
kubectl delete Service my-nginx-svc -n my-nginx-namespace
kubectl delete ALBIngress my-albingress -n my-nginx-namespace
kubectl delete AlbConfig alb
kubectl delete IngressClass alb

After deleting the above resources, delete the namespace to remove any remaining objects:

kubectl delete namespace my-nginx-namespace

Related topics

• Deploy a workload — detailed workload creation parameters.

• Recommended workload configurations — production configuration guidance.

• Configure certificates for HTTPS — set up SSL/TLS for encrypted traffic.

• ALB Ingress configuration with annotations — customize ALB behavior using annotations.