Cloud ECS nodes in ACK Edge clusters - Container Service for Kubernetes

We recommend that an ACK Edge cluster includes at least two cloud ECS nodes. This topic describes their purpose and explains how to deploy workloads to them.

Purpose of cloud nodes

An ACK Edge cluster runs numerous system components to allow cluster resources to interact with the API Server and other cloud services. For security and stability, these components must be deployed on cloud ECS nodes:

Important

Clusters running version 1.30.7-aliyun.1 or earlier require at least one cloud node to create an edge node pool.

Component	Required
metrics-server	Yes
yurt-app-manager	Required for cluster versions 1.30 and earlier
raven-agent-ds	Required if cluster resources need public network access
logtail-ds	No
loongcollector	No
ack-arms-prometheus	No
migrate-controller	No
alicloud-monitor-controller	No
ack-kubernetes-cronhpa-controller	No
ack-node-problem-detector	No
ack-onepilot	No
csi-provisioner	No
storage-operator	No
ack-arms-cmonitor	No
policy-template-controller	No
security-inspector	No
ack-koordinator (ack-slo-manager)	No
ack-vertical-pod-autoscaler	No
Argo Workflows	No
kritis-validation-hook	No

Deploy workloads to cloud nodes

By default, cloud ECS nodes in an ACK Edge cluster have the alibabacloud.com/is-edge-worker: 'false' label. To deploy a workload to a cloud ECS node, configure the workload's nodeSelector to match this label:

      ...
      nodeSelector:
        alibabacloud.com/is-edge-worker: 'false'
      ...

As a best practice, deploy controllers and webhooks that frequently interact with the API Server on cloud nodes.