Docs

Volcengine Kubernetes Engine

Clusters

Viewing cluster information

After a cluster is created, you can view and manage cluster information in the Basic information section, including cluster information, resource usage, network information, node information, connection information, and event information.

Prerequisites

The target cluster is in the Running state.

Viewing and managing clusters

In the left navigation bar, click Cluster. In the right part of the page, click the target cluster name to go to its management page.

Select Overview in the left navigation pane, and then you can view the general information and manage configurations of the current cluster by switching among the tabs on the Overview page.

Overview

Node information

Connection information

K8s events

Control plane parameter configuration

Control plane observability

Basic information

It includes the name, ID, status, Kubernetes version of the cluster or node, and local domain name. The items listed in the following table are configurable.

Parameter	Description
Name	Cluster name. Click the edit icon to change the cluster name.
Deletion protection	Enable or disable cluster deletion protection. If enabled, the cluster cannot be deleted through either the console or API. It can prevent accidental deletion of clusters.
Cluster Specifications	Configure the cluster control plane specifications. For details, see Preset control plane.
Project	Display the project to which the cluster belongs. Click the project name to navigate to the details page for the current project, where you can view resources under the project or manage project permissions. For details, see Resource project management.
Description	Cluster description. Click the edit icon to add or modify the cluster description.
Tags	Cluster resource label (Tag). Click the edit icon to add or modify cluster labels.
IRSA OIDC	IRSA (IAM Role for Service Account) switch for the cluster. For details, see IRSA overview.
Custom certificate SAN	Allows you specify custom IP addresses, domain names, or URIs that meet the requirements. Click the edit icon to add or modify the custom certificate SAN. tip Modifying configuration of SAN certificate will lead to a quick restart of cluster API server. We recommend doing it during low-traffic periods.

Cluster network configuration

Parameter	Description
VPC	The VPC to which the current cluster belongs. Click the VPC name to go to the VPC console and view and manage VPCs associated with the cluster. For details, see What is VPC.
Network model	The network model of the current cluster (CNI). For details, see Pod networking.
Pod CIDR	It is displayed only if the cluster is running on a Flannel network. This refers to the CIDR (Classless Inter-Domain Routing) for pods (container groups) in the Flannel cluster. CIDR is an IP address allocation method.
Pod subnets	It is displayed only if the cluster is running on a VPC-CNI network. In a VPC-CNI cluster, if the existing pod subnet has insufficient IP addresses, you can add additional pod subnets to the pod network. Click Add to select subnets available on the VPC where the cluster is running. Click Remove to remove Pod subnets that are not used by resources within the cluster.
Service CIDRv4	IPv4 CIDR address for the services in the cluster.
Single-node Pod upper limit	It is displayed only if the cluster is running on a Flannel network. The maximum number of pods that a single node in a Flannel cluster can have.
Service forwarding mode	The forwarding mode of the current cluster. There are two modes available in VKE currently: ipvs: IPVS (IP Virtual Server) mode. This mode is applicable to flannel clusters. eBPF: eBPF mode. This mode is applicable to VPC-CNI cluster.
Default security group for nodes	The default security group for nodes in the current cluster. It is named with the pattern <cluster ID>-common (for example, cc9l5hi6rsfek********-common). For details, see Security group settings. Click the security group name to redirect to the VPC console, where you can view and manage the security groups associated with the cluster. For details, see Security groups. warning We recommend managing and operating security groups with caution. Modifications to the default node security groups can cause access failures for associated nodes.
Default security group for pods	It is displayed only if the cluster is running on a VPC-CNI network. In addition to providing default node security groups, the VPC-CNI cluster also automatically creates a default pod security group named with the pattern <clusterID>-pod (for example, cc9l5hi6rsfek********-pod). This group is used to configure security group policies for pods. For details, see Security group settings. Click the security group name to go to VPC console – Security group to view and manage security groups associated with the cluster. For details, see Security groups. warning We recommend managing and operating security groups with caution. Modifications to the default pod security groups can cause access failures for business.
NAT gateway	The NAT Gateway associated with the cluster allows nodes and applications within the cluster to access the public network. Click the NAT Gateway name to be redirected to the NAT Gateway console, where you can view and manage the NAT Gateways associated with the cluster. For details, see What is a NAT Gateway? Click Close to disable the public access feature for the cluster. After you disable this feature, the cluster will automatically clean up the route entries for the NAT Gateway instance. If the NAT Gateway instance is not reused, it will also be deleted. You can enable Public NAT for internet endpoint when creating a cluster. To learn how to enable it after creating, see FAQ. tip This parameter is displayed for clusters with Public NAT for internet endpoint enabled during creation. You can use this parameter to disable the created managed NAT gateway for the cluster. For details, see Creating clusters. If you did not enable Public NAT for internet endpoint when you created the cluster, but configured a NAT gateway for the cluster manually or through operation and maintenance, this parameter will not be displayed, and you cannot delete the corresponding NAT gateway by using this parameter.

Cluster API server configuration

Parameter	Description
Control plane subnets	The network segments used when creating load balancers for Kubernetes API servers. Hovering your mouse over a subnet name can display its basic information. Clicking a subnet name will take you to the VPC console, where you can view the subnet details. Clicking Add will display a slide-out panel providing a list of available subnets. warning To ensure high availability of the cluster, we recommend selecting subnets (if necessary) from different availability zones. There will be a quick restart of the API server after subnets are added. Do not take any actions on the cluster during the restart.
Private access	The private network address of the API Server of the current cluster.
Internet access to API Server	The public IP of the current API Server. You can enable or disable Internet access to the API Server as needed.
CLB	The name of the LoadBalancer (CLB) instance associated with the current cluster API Server. Click the LoadBalancer name to go to the LoadBalancer console, where you can view and manage LoadBalancer instances associated with the cluster. For details, see What is LoadBalancer.

Cluster risk overview

If cluster inspection is not configured:

Click Inspection to manually start a cluster inspection job and view the cluster risk overview.

Select Scheduled inspection > Set scheduled inspection to create a custom inspection job. For details, see Configuring cluster inspection.

If cluster inspection is already performed or scheduled:

Click View details to be redirected to the cluster inspection console, where you can view the cluster inspection results.

Click Re-inspection to start another inspection immediately. After the inspection ends, you can view the latest inspection results and risk status of the cluster.

Resource usage

It displays the CPU and memory usage of Elastic Compute Service (ECS) and Volcengine Container Instance (VCI) in the cluster. The following table contains descriptions of usage information.

tip

Total node resources in the following formula indicate the sum of the CPU or memory of all worker nodes in the cluster.

Parameter	Description
ECS resource usage
Usage	CPU or memory usage of all worker nodes in the cluster.
Remaining available	The remaining available CPU/memory of all worker nodes in the cluster, which is calculated by using the following formula: Remaining available resources = Total node resources - Unschedulable resources - Used resources.
Unschedulable	The unschedulable resource quota from the total resource amount allocated for all the worker nodes in a cluster, which usually refers to the reserved resources for nodes. For details, see Policy for node reserved resources.
VCI resource usage
Instance family	Select a VCI instance family from the drop-down menu to view the resources used for that instance family, which include CPU, memory, GPU, and the number of VCI instances.

Last updated: 2026.10.20 14:03:08