ACK Edge clusters support edge node autonomy. Edge node autonomy ensures that applications on an edge node can still run as expected when the edge node is disconnected from the cloud and no application pod is evicted or migrated to other edge nodes. When a node with node autonomy disabled disconnects from the cloud, the application pods on the node are evicted after the tolerance time ends. This topic describes how to configure node autonomy for edge nodes in the Container Service for Kubernetes (ACK) console.
Prerequisites
Background information
You can enable or disable node autonomy for edge nodes. By default, node autonomy is disabled for edge nodes that are newly added to a cluster.
When an edge node with node autonomy enabled disconnects from the cloud, the system ensures that the application pods on the node are not evicted and the applications can automatically recover from the exception. Node autonomy is suitable for edge computing scenarios where the network connection is weak.
When an edge node with node autonomy disabled disconnects from the cloud, the node cannot send heartbeats to the control planes in the cloud. As a result, the status of the node changes to Not ready and the application pods on the node are evicted or migrated to other edge nodes after the toleration time ends.
Procedure
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of the cluster that you want to manage and choose in the left-side navigation pane.
On the Nodes page, find the node that you want to manage, and choose in the Actions column.
NoteNode Autonomy Setting is displayed only if the current node is an edge node.
In the Node Autonomy Setting dialog box, click OK.