This document describes how to deploy virtual node in the cluster through the TKE console, and deploy the cluster workload as an elastic container.
Pods scheduled to the virtual node will be billed based on the amount of resources that the Pods apply for and the actual use period. For details, please see Elastic Clusters Billing Overview, Elastic Clusters Product Pricing, and Elastic Clusters Purchase Limits.
This configuration item is specified at the cluster level and therefore cannot be modified after configuration.
- The security group configured for the virtual node is directly associated with Pods in the node. Please configure the network rules as required by the pods. For example, you need to open port 80 if the pods provide service via port 80.
- This security group is the default security group bound to the Pod that is scheduled to the virtual node. You can specify other security group during scheduling. For more information, see Notes on Scheduling Pod to Virtual Node.
- It is recommended to select the subnets of multiple AZs to ensure availability.
- A corresponding virtual node will be generated for each selected subnet. When Pod is scheduled in batches, it will be automatically distributed on multiple virtual nodes (subnets) by default.
Tolerations. You can specify this parameter for all the virtual nodes of the node pool so that Pods that do not meet the relevant conditions cannot be scheduled to these nodes and any such Pods already on these nodes will be drained.
The value of Taints usually consists of
effect. Valid values of
- PreferNoSchedule: optional condition. Try not to schedule a Pod to a node with a taint that cannot be tolerated by the Pod.
- NoSchedule: when a node contains a taint, a Pod without the corresponding toleration must not be scheduled.
- NoExecute: when a node contains a taint, a Pod without the corresponding toleration to the taint will not be scheduled to the node and any such Pods already on the node will be drained.
Assume that Taints is set to
key1=value1:PreferNoSchedule. The following figure shows the configurations in the TKE console:
After the creation of the virtual node, please refer to Managing a Virtual Node for the subsequent management of the node pool.