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 Kubernetes EngineAPI referenceCall methodsResponse result
Copy page
Download PDFCall methods
Response result
Copy pageDownload PDFResponse result
After you call the APIs of Volcano Engine, all response results will include fields, such as RequestId, Action, Version, Service, and Region.
Sample success responses
After an API is called, the request ID and the API response parameters will be returned. The HTTP status code is 2xx.
{
"ResponseMetadata": {
"RequestId": "2020102017223001022507",
"Action": "{Action}",
"Version": "{Version}",
"Service": "{Service}",
"Region": "{Region}"
},
"Result":"..."
}
After the request is processed as expected, the response result will include two parts: ResponseMetadata and Result. The Result varies based on the different APIs. The following table describes fields.
Parameter | Description |
Parameter | Description |
RequestID | The unique identifier for each API request. |
Action | The name of the API, which is a public parameter of the request. |
Version | The version number, which is a public parameter of the request. |
Service | The requested service, which is a public parameter of the request. |
Region | The region, which is a public parameter of the request. For more information about regions, see Regions and availability zones. |
Sample error responses
If an error occurs when you call an API, the request ID and an error message will be returned. The HTTP status code is 4xx or 5xx. You can troubleshoot based on the API error code and error message. For detailed information, see Public error codes and Error code documentation for the specific API.
{
"ResponseMetadata": {
"RequestId": "202010201722300102****",
"Action": "{Action}",
"Version": "{Version}",
"Service": "{Service}",
"Region": "{Region}",
"Error": {
"Code": "InvalidActionOrVersion",
"Message": "Could not find operation GetUserById for version 2018-01-01"
}
}
}
Last updated: 2026.07.23 14:31:46
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
