FAQ

• How can I rename SLB instances if the Cloud Controller Manager (CCM) version is V1.9.3.10 or earlier?
• Which network plug-in do I need to choose for an ACK cluster, Terway or Flannel?
• How do I manually install alicloud-application-controller?
• Can I use hostPorts to create port mappings in an ACK cluster?
• How does CCM calculate node weights in Local mode?

How can I rename SLB instances if the Cloud Controller Manager (CCM) version is V1.9.3.10 or earlier?

1. Log on to a master node in a Container Service for Kubernetes (ACK) cluster. For more information, see Use kubectl to connect to an ACK cluster.
2. Run the # kubectl get svc -n ${namespace} ${service} command to view the service type and service IP address.
   Note Replace ${namespace} and ${service} with the cluster namespace and service name.
3. Run the following command to generate a tag for the SLB instance:

   kubectl get svc -n ${namespace} ${service} -o jsonpath="{.metadata.uid}"|awk -F "-" '{print "kubernetes.do.not.delete: "substr("a"$1$2$3$4$5,1,32)}'

   
4. Log on to the SLB console, select the region where the SLB instance is deployed, and then use the IP address that is returned in Step 2 to find the specified SLB instance.
5. Add the tag that is generated in Step 3 to the SLB instance. Callout 1 in the preceding figure shows the tag key, and callout 2 shows the tag value. For more information, see Add a tag.

Which network plug-in do I need to choose for an ACK cluster, Terway or Flannel?

Two network plug-ins are used to create an ACK cluster: Flannel and Terway.

How do I manually install alicloud-application-controller?

For Kubernetes V1.10.4 and later, alicloud-application-controller is automatically installed to enable phased releases based on custom resource definitions (CRDs).

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: alicloud-application-controller
  labels:
    owner: aliyun
    app: alicloud-application-controller
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      owner: aliyun
      app: alicloud-application-controller
  template:
    metadata:
      labels:
        owner: aliyun
        app: alicloud-application-controller
      annotations:
        scheduler.alpha.kubernetes.io/critical-pod: ''
    spec:
      tolerations:
      - effect: NoSchedule
        operator: Exists
        key: node-role.kubernetes.io/master
      - effect: NoSchedule
        operator: Exists
        key: node.cloudprovider.kubernetes.io/uninitialized
      containers:
        - name: alicloud-application-controller
          image: registry.cn-hangzhou.aliyuncs.com/acs/aliyun-app-lifecycle-manager:0.1-c8d5da8
          imagePullPolicy: IfNotPresent
      serviceAccount: admin

Can I use hostPorts to create port mappings in an ACK cluster?

• No, you cannot use hostPorts to create port mappings in an ACK cluster.
• A pod in a VPC can be accessed by other cloud resources deployed in the same VPC through the endpoint of the pod in the VPC. Therefore, port mapping is not required.
• If the service type is NodePort or LoadBalancer, you can make a service accessible over the Internet.

How does CCM calculate node weights in Local mode?

Assume that pods with the app=nginx label are deployed on three Elastic Compute Service (ECS) instances. In the following figure, when externalTrafficPolicy is set to Local, the pods provide services for external users by using Service A. The following sections describe how node weights are calculated.

• For CCM V1.9.3.164-g2105d2e-aliyun and later

  Assume that the CCM version is earlier than V1.9.3.164-g2105d2e-aliyun. The following figure shows that the weight of each ECS instance in Local mode is 100. This indicates that traffic loads are evenly distributed to the ECS instances. However, the loads of the pods are different because the pods are unevenly deployed on the ECS instances. For example, the pod on ECS 1 has the heaviest load and the pods on ECS 3 have the lightest load.

  

• For CCM versions later than V1.9.3.164-g2105d2e-aliyun and earlier than V1.9.3.276-g372aa98-aliyun

  For CCM versions later than V1.9.3.276-g372aa98-aliyun and earlier than V1.9.3.164-g2105d2e-aliyun, the node weights are calculated based on the number of pods deployed on each node. The weights of the ECS instances are 16, 33, and 50. Therefore, traffic loads are distributed to the ECS instances at the ratio of 1:2:3.

  Calculation formula:

  

• For CCM V1.9.3.276-g372aa98-aliyun and later

  The weight calculation in the preceding figure still has a slight imbalance due to the precision of the calculation formula. For CCM V1.9.3.276-g372aa98-aliyun and later, the weight of each node equals the number of pods deployed on the node. In the following figure, the weights of the ECS instances are 1, 2, and 3. Traffic loads are distributed to the ECS instances at the ratio of 1:2:3. The pods have a more balanced load than those in the preceding figure.

  Calculation formula: