Docs

Volcengine Kubernetes Engine

Self-managed/third-party cluster uses virtual node

Creating virtual nodes

By registering and managing virtual nodes on the cloud, VCI elastically schedules resources for business workloads in Kubernetes clusters to the cloud, fully expanding the computing resource capacity of on-premises clusters. This topic describes how to create virtual nodes by using the console.

tip

[Beta - apply for trial]: This feature is currently at the beta stage. Submit an application if you need to use it.

Prerequisites

Virtual nodes support association with self-managed Kubernetes clusters and VKE clusters. Before creating a virtual node, you need to obtain the Kubeconfig file for the target cluster:

Kubeconfig for self-managed Kubernetes clusters: It can be obtained by using an account with admin permissions.

Kubeconfig for VKE clusters: For detailed instructions, see Managing cluster access credentials.

Procedure

In the left navigation pane, click Volcengine Container Instance > Virtual node, and then click Create virtual node.

On the Create virtual node page, specify the required parameters in the Virtual node configuration step.

Parameter	Description
Basic configuration
Name	Set a name for the virtual node based on on-screen prompts. The name must be unique within the same VPC.
VPC	Select a VPC for the virtual node. A VPC provides an isolated, self-configurable, and self-managed virtual network environment for virtual nodes. If no VPC is available, follow the steps described in Creating VPC to create one.
Subnet	Select a subnet under the selected VPC to provide a subnet segment for the virtual node network. If there are no available subnets, click Creating subnets to create one. For details, see Creating subnets.
Security group	Select the security group for the virtual node network to ensure the security and normal functionality of the virtual node.
Target cluster configuration
Kubeconfig	The KubeConfig of the target Kubernetes cluster to which the virtual node will connect.
Node configuration
Node label	Labels in VKE function identically to Kubernetes labels. Labels can be used to define attributes for virtual nodes. These attributes facilitate node filtering. Click Add node labels and enter a key and its value.
Taint	Taints allow a virtual node to evict specific pods and therefore prevent those pods from being scheduled to the virtual node. Click Add taint and enter the Key, Value, and Effect based on prompts. You can specify one of the following effects for a taint: NoSchedule: If a node has a taint whose effect is NoSchedule, the system does not schedule pods to the node. NoExecute: Pods that do not tolerate this taint are evicted from nodes with this effect; pods that tolerate it are not evicted. PreferNoSchedule: The system attempts to avoid scheduling pods to nodes with taints that are not tolerated by the pods, but it is not guaranteed.

Click Next: Configuration confirmation to confirm the virtual node configuration and read the terms of service.

If you confirm the configuration and have no objections to the terms of service, select the I have read and agree to Volcengine Kubernetes Engine Specific Terms of Service checkbox and click Confirm to create the virtual node.

tip

Creating the virtual node is expected to take 5 minutes. Please wait patiently. When the status changes to Running, the virtual node has been created successfully. You can start using the elastic scheduling capabilities of VCI resources.