Docs

Volcengine Kubernetes Engine

Billing

Tag-based bill splitting

VCI supports bill splitting based on tags added to instances. This addresses the need for financial cost sharing.

Usage instructions

When using system tags for bill splitting, you need to enable bill tags in the billing center console at Billing management - Bill tags and apply the corresponding tags to the bill details. For details, see Cost tags and Tag-based bill splitting.

tip

Enabled system tags will be automatically synchronized to split bills, but there may be up to an 8-hour delay.

System tag	Description
sys:vke:cluster-id-{real cluster ID}	The ID of the VKE cluster to which the VCI pod belongs. Example: sys:vke:cluster-id-ccofrscb915********.
sys:vke:namespace	The namespace where the VCI pod is located.
sys:vke:zone-id	The ID of the availability zone where the VCI pod is located, for example, cn-beijing-a.
sys:vke:pod-name	The name of the VCI pod.
sys:vke:owner-reference-kind	The kind of workload that the VCI pod belongs to, such as Deployment and Job.
sys:vke:owner-reference-name	The name of the workload (for example, Deployment, and Job) to which the VCI pod belongs.
sys:vke:instance-type	Specifications of the VCI pod. For example, sys:vke:instance-type: vci.u1.2c-4gi.

Adding tags

Enable tag-based bill splitting in VCI pods via pod annotations.

tip

You can add resource tags in the Volcano Engine Resource management console, or directly add resource tags when creating VCI pods. The system will synchronize the tags to the Resource management console - Tags page. For details, see Managing tags and resources.

Annotation Key	Annotation sample value	Description
vci.vke.volcengine.com/resource-tags	"app:nginx,env:test"	Specify custom tags for the VCI pod to enable bill splitting of VCI resources by tag. The requirements for custom tags are as follows: The supported format is string. Each tag consists of a key-value pair in the key:value format. Multiple tags are separated by commas (,). For example, "app:nginx,env:test" means that two tags are set for the VCI pod: app:nginx and env:test. The requirements for a tag key are as follows: It must not start with volc: in any case. It can only contain language characters, digits, spaces, and the following special characters: _./=+-@. The length is limited to 1 to 128 characters. The requirements for a tag value are as follows: This can be left blank. It can only contain letters, digits, spaces, and the following special characters: _./=+-@. Its length does not exceed 256 characters. A single VCI pod supports up to 50 tags. Adding a tag with the same key as an existing tag key by using the annotation will overwrite the original tag value. Tag keys and values do not allow leading or trailing spaces.

The following sample code creates a VCI pod. For more information about creating VCI pods, see Creating instances:

Viewing results after configuring bill splitting

Custom VCI tags will only be shown in the Tags column on the Split bills page. You can follow the steps below to view the result:

On the Split bills page, use the Tags search box at the top of the page to search for the custom VCI pod tags that you have set.

Last updated: 2026.07.24 16:18:02