Configure ACS computing power with the eci-profile ConfigMap

Overview

The eci-profile ConfigMap automatically injects pod configurations such as vSwitches, security groups, and DNS resolution modes. You can also update these configurations as needed.

• You do not need to restart the acs-virtual-node component to update the configurations.

• The updated configurations are immediately applied to newly created ACS pods, but are applied to existing ACS pods only after rolling releases are performed on the pods.

Usage notes

During pod creation, the system reads the eci-profile ConfigMap in the kube-system namespace and applies its configurations. View the eci-profile YAML:

kubectl get cm -n kube-system eci-profile -o yaml

Example eci-profile YAML:

apiVersion: v1
kind: ConfigMap
metadata:
  name: eci-profile
  namespace: kube-system
data:
  enablePrivateZone: "false"
  securityGroupId: sg-2zeeyaaxlkq9sppl****
  vSwitchIds: vsw-2ze23nqzig8inprou****,vsw-2ze94pjtfuj9vaymf****
  vpcId: vpc-2zeghwzptn5zii0w7****
  selectors: ""

To modify the eci-profile, use one of the following methods:

• Run the kubectl edit command:

  kubectl edit configmap eci-profile -n kube-system

• Use the ACS console:

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

  2. On the Clusters page, click the name of your cluster. In the left navigation pane, click Configurations > ConfigMaps.

  3. On the ConfigMap page, select the kube-system from the Namespace drop-down list. Find the eci-profile ConfigMap and click Edit YAML in the Actions column.

     Note

     If the modified eci-profile contains a formatting error, the configuration does not take effect. View the error by running the following command:

     kubectl -n kube-system get event --field-selector involvedObject.namespace=kube-system,involvedObject.name=eci-profile

Update cluster parameters

The eci-profile ConfigMap contains cluster parameters such as vpcId (VPC) and vSwitchIds (vSwitches). You can update these parameters as needed, and changes take effect immediately. The following table lists the configurable parameters.

Configure selectors

Selectors let you inject additional annotations and labels into specific pods based on their namespace or pod labels, without modifying those pods' YAML files.

When ACS creates a pod, it evaluates each selector in order. For each selector whose criteria match the pod, ACS merges the effect settings (annotations and labels) into the pod. Annotations and labels already present on the pod are never overwritten.

Example selector configuration:

apiVersion: v1
kind: ConfigMap
metadata:
  name: eci-profile
  namespace: kube-system
data:
  selectors: |
    [
      {
        "name": "selector-demo1",
        "namespaceSelector": {
          "matchLabels": {
            "kubernetes.io/metadata.name": "dev-ns"
          }
        },
        "objectSelector": {
          "matchLabels": {
            "acs": "true"
          },
          "matchExpressions": [
            {
              "key": "usage",
              "operator": "In",
              "values": ["testing"]
            }
          ]
        },
        "effect": {
          "annotations": {
            "network.alibabacloud.com/custom-dnsconfig": "{\"servers\":[\"114.114.114.114\",\"8.8.8.8\"],\"searches\":[\"xx.com\",\"yy.com\"],\"options\":[\"ndots:2\",\"edns0\"]}"
          },
          "labels": {
            "created-by-acs": "true"
          }
        }
      }
    ]

The selector-demo1 selector provides these capabilities:

Examples

1. Create a Deployment that matches the selector-demo1 conditions:

   apiVersion: v1
   kind: Pod
   metadata:
     name: nginx
     namespace: dev-ns
     labels:
       alibabacloud.com/acs: 'true'
       alibabacloud.com/compute-class: general-purpose
       alibabacloud.com/compute-qos: default  
       acs: "true"
       usage: "testing"
   spec:
     containers:
     - name: nginx
       image: anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6
       command: ["sleep", "infinity"]
       ports:
       - containerPort: 80

2. After creating the Deployment, view the pod information in the ACS console.

   The Pod details page shows the basic information of the Pod: the name is nginx, the namespace is dev-ns, the status is Running, the node is virtual-kubelet-cn-hangzhou-h, and the Pod IP is 192.168.8.30. The labels include created-by-acs: true, which indicates that the Pod is created by ACS. The value of the network.alibabacloud.com/custom-dnsconfig Annotation contains the custom DNS configuration, where servers is ["114.114.114.114", "8.8.8.8"].