After you enable the virtual node-based pod scheduling policy, pods in your ACK Serverless cluster can be scheduled based on Kubernetes pod affinity, node affinity, and inter-region topology spreading to improve application availability and reduce network latency.
Prerequisites
An ACK Serverless Pro cluster that runs Kubernetes 1.22 or later is created. For more information, see Create an ACK Serverless cluster and Update an ACK cluster.
Usage notes
If you configure pod anti-affinity for a pod, the pod may fail to be scheduled. Proceed with caution.
If you configure virtual node anti-affinity for a pod, the pod may fail to be scheduled. Proceed with caution.
During pod scheduling, the system queries the inventory information and updates the cluster status. After the virtual node-based pod scheduling policy is enabled, each pod can be scheduled 1 second faster than before. Up to 300 pods can be scheduled concurrently per second. Assess the impacts before you enable the virtual node-based pod scheduling policy if you want to schedule large numbers of pods concurrently within a short period of time.
Step 1: Verify that the components of the required versions are installed
The virtual node-based pod scheduling policy depends on the Kube Scheduler and ACK Virtual Node components. The versions of both components must meet the requirement. Perform the following steps to verify that the components of the required versions are installed
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.
In the Core Components section, verify that the components of the following versions are installed. If not, click Install or Upgrade in the cards of the components to install or update the components.
Kube Scheduler: 5.9 or later
ACK Virtual Node: 2.10.0 or later
Step 2: Enable the virtual node-based pod scheduling policy
Click Configuration in the lower-right corner of the Kube Scheduler card.
Select Enable Virtual Node-based Pod Scheduling and click OK.
