Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
Document
Volcengine Kubernetes Engine
What's New
History feature release notes
Kubernetes version release notes
Containerd runtime release notes
Add-on release notes
Monitoring add-ons
Scheduling add-ons
DNS add-ons
Security add-ons
GPU add-ons
Sandbox add-on
Security announcements
Product Announcement
Historical announcements
Overview
Getting started
User guide
Clusters
Creating clusters
Connecting to clusters
Upgrading clusters
Node pool
Creating node pools
Scaling out/in node pools
Nodes
Authorization management
Image
Namespaces
Networking
Cluster network
Container Network
Service
LoadBalancer
CLB
Ingress
APIG Ingress
ALB Ingress
Customize ALB Ingress forwarding rules
Certificate and security
CLB Ingress
Nginx Ingress
Gateway API
Workloads
Creating workloads
Configure workloads
Pods
Configuration management
Image acceleration
Storage
FSX client
EBS Volumes
TOS Volumes
NAS volumes
FSX access methods
NFS access methods
EFS volumes
vePFS volumes
FSX access methods
vePFS Client access methods
NFS access methods
CloudFS volumes
Local volumes
Autoscale
Node autoscaler
Workload autoscaler
Horizontal Pod Autoscaler (HPA)
Cron Horizontal Pod Autoscaler (CronHPA)
Intelligent Horizontal Pod Autoscaler (IHPA)
Horizontal Pod Autoscaler based on event-driven (KEDA)
Add-on management
Network add-ons
Storage add-ons
Monitoring add-ons
Scheduling add-ons
DNS add-ons
GPU add-ons
Core add-ons
Sandbox add-on
Upgrading add-ons
Heterogeneous computing
NVIDIA GPU
mGPU scheduling
RDMA high-performance computing
Scheduling management
Topology-aware scheduling
QoS-aware scheduling
Observability
Log management
Basic observation
Setup & Configuration
Cluster observation
Storage observation
Other observation
Using metrics
Full stack observation
Alert management
Diagnosis and inspection
Node check and self-healing
Application center
Backup center
Stability
Large-scale cluster management
Best practices
Authorization
Clusters
Nodes and node pools
Networking
Storage
Scheduling
Observability
Solution
Security and compliance
API reference
Cluster management
NodePool management
Node management
Virtual nodes management
Add-on management
Tag management
Access policy management
Instance images management
Cloud native observability
Inspection and diagnosis
Task management
Volcengine Container Instance
Appendix
SDK reference
Development guide
Terraform
FAQs
General FAQs
Cluster FAQ
cluster management
cluster network
cluster upgrade
Node and Node pool FAQs
Authorization FAQs
Workload FAQs
Service and Ingress FAQs
Storage FAQs
Heterogeneous computing FAQs
Observability FAQs
Quota FAQs
Add-on FAQs
Cloud-native AI
ServingKit
LLM applications
ComfyUI application
Deploying the Al inference application through Helm
Deepseek practices
Qwen practices
Kimi practice
Seed practices
Best practices
DeepSeek model deployment
GLM model deployment
MiniMax model deployment
Qwen model deployment
Kimi model deployment
Volcengine Container Instance
What's new
Historical feature release notes
Product Announcement
Overview
Billing
User guide
Integrating with VCI
Virtual node
VKE cluster uses virtual nodes
Self-managed/third-party cluster uses virtual node
Creating an instance
General purpose instance
GPU-accelerated computing instance
VCI Agent Sandbox
Startup acceleration
E2B-based management
Upgrade guide
Networking
Monitoring
Scheduling
Container configuration
VCI Image Cache
Best practices
Security and compliance
FAQs
- Documentation
Volcengine Kubernetes EngineVolcengine Container InstanceBillingProject-based bill splitting
Copy page
Download PDFBilling
Project-based bill splitting
Copy pageDownload PDFProject-based bill splitting
VCI supports classification of VCI pods by project. This topic describes how to classify and manage VCI resources from the project dimension to address the issue of financial cost allocation.
Prerequisites
To use a project other than default, ensure that the project has been created. For more information about projects, see Project management.
Specifying projects for VCI pods
Specify the project to which a VCI Pod belongs by using a pod annotation.
Annotation Key | Type | Annotation sample value | Description |
Annotation Key | Type | Annotation sample value | Description |
vci.vke.volcengine.com/project-name | String | test-project | The name of the project to which the VCI pod belongs. |
Tip
- When creating a VCI pod, if the project to which the VCI pod belongs is not specified with this annotation:
- If the VCI pod is created in a VKE cluster, it belongs by default to the project of the VKE cluster. If the cluster does not belong to any project, the VCI pod will belong to the default project.
- If the VCI pod is created according to Using VCI elastically in self-hosted Kubernetes clusters, the VCI pod will belong to the default project.
- VCI also supports appending this annotation to the VCI pod by using the vci-profile file. For information about vci-profile, see Using VCI by configuring vci-profile.
The following sample code creates a VCI pod. For more information about creating VCI pods, see Creating instances.
apiVersion: v1
kind: Pod
metadata:
name: demo-vci-pod # Pod Name.
namespace: default # Namespace to which the pods belong.
annotations:
vke.volcengine.com/burst-to-vci: enforce # Force the use of VCI.
vke.volcengine.com/preferred-subnet-ids: subnet-3tispp1n******** # Specify the ID of a subnet. You can specify multiple subnets within the same availability zone. To do so, separate them with commas (,).
vci.vke.volcengine.com/preferred-instance-family: vci.u1 # Specify the instance family of the VCI.
vci.vke.volcengine.com/project-name: doc-project # The project to which the VCI pod belongs.
spec:
containers:
- image: cr-cn-beijing.volces.com/tw/nginx:1.0 # The address and version of the container image. Replace the value with your actual information.
imagePullPolicy: Always
name: nginx
resources:
requests: # Specify the vCPU, memory, and GPU settings for the container as needed.
cpu: 2
nvidia.com/gpu: 2 # Specify the number of GPUs for the container as needed (same as native one). You can specify both limits and requests, but the values must be equal.
limits:
cpu: 2
nvidia.com/gpu: 2
Viewing results after configuring bill splitting
After you specify the project for the VCI pod, the project will be shown in the Project column on the Split Bills page. You can query the result by using the following steps:
- Log in to the Volcano Engine Cost Center.
- Select Bill management > Split bills in the left navigation bar.
- On the Split bills page, view the project to which the VCI pod bill belongs in the Project column.
tip
After the split bills are issued, the project information will not be immediately reflected on the bills. There will be a delay of 3 to 4 hours.
Last updated: 2026.03.16 14:55:25
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
