You need to enable JavaScript to run this app.
Volcengine Kubernetes Engine

Volcengine Kubernetes Engine

Copy page
Download PDF
Storage add-ons
csi-vepfs
Copy page
Download PDF
csi-vepfs
The csi-vepfs add-on is a vePFS driver implemented based on the CSI specification. This topic describes how to install and upgrade the csi-vepfs add-on and provides relevant considerations.​
Add-on overview​
csi-vepfs is a storage add-on provided by VKE for mounting vePFS to Pods in clusters. This add-on delivers ‌ultra-high throughput and ultra-low latency‌ shared filesystem access for scenarios such as high-performance computing (HPC) and large-scale AI model training.​
As a ‌non-managed component‌, it runs on your cluster nodes and consumes a small amount of node-level compute resources. After the add-on is installed, the following Kubernetes resources will be automatically created in the kube-system namespace.​
​
Resource name​
Resource type​
Resource description​
csi-vepfs-controller​
Deployment​
The Pod for the vePFS management controller. It is responsible for monitoring storage requirements (PVCs/PVs) within the cluster and interacting with vePFS to maintain node consistency after storage mounting in the cluster.​
csi-vepfs-node​
DaemonSet​
The Pod for the vePFS mount service. It runs on each worker node in the cluster and is responsible for executing specific mount actions on the node side to mount storage as a filesystem available to containers.​
​
tip​
The preceding table only lists the main resources of the add-on, as well as resources that may be used when the add-on or the corresponding feature is configured. This helps you understand the main components of this add-on. Other resources, such as ConfigMap and Secret, related to the add-on are not described here. You should refer to the actual resources in the cluster.​
Add-on versions​
For information about the historical release records of the add-on, as well as new features and optimization descriptions for each version, see Add-on release records.​
Install the add-on​
  1. Log in to the VKE console.​
  1. In the left navigation bar, click Cluster. Click the target cluster name to go to the management page of this cluster.​
  1. In the left navigation pane, select Addons and click the Storage tab.​
  1. Move the pointer over the add-on card, click Deploy, and configure the add-on parameters.​
  • ​
    Parameter​
    Description​
    Node Label Selector​
    This parameter can be specified only when the Deployment form parameter is set to Elastic Compute Service deployment. After you enable this feature, you can specify node labels, and the core workloads of the add-on will be scheduled onto nodes with the specified labels.​
    Pod scheduling based on taints and tolerations​
    This parameter can be specified only when the Deployment form parameter is set to Elastic Compute Service deployment. After it is enabled, you can configure taint tolerations, allowing the core workloads of the add-on to be scheduled to nodes with the specified taints.​
    Node Resource configuration​
    Specify the CPU requests, CPU limits, memory requests, and memory limits of various resources in the add-on.​
    ​
  1. Click Confirm to finish configuration.​
Upgrading add-ons​
New versions of the add-on are released at irregular intervals to provide new features or fix known issues. When the add-on card displays that a new version is available, we recommend upgrading the add-on promptly. To ensure a smooth service transition, perform the upgrade during off-peak hours whenever possible. For upgrade procedures and considerations, see Upgrading add-ons.​
Monitoring and alerting​
Add-on observability​
The stability and performance of the csi-vepfs add-on directly affect its proper functioning and overall effectiveness. We recommend enabling add-on observability in your cluster to monitor add-on health in real time. For details, see VKE observability.​
Configuring alerts​
VKE provides comprehensive cluster monitoring and alerting capabilities based on VMP. You can quickly create alert rule groups by using system preset templates or configure custom alert rules by using PromQL statements based on your business requirements. You can also export preset templates in YAML format, adjust the rules, and save them as custom alert templates for reuse across multiple clusters. For details, see the following topics:​
Related documentation​
​
​
Last updated: 2026.09.03 10:38:28