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 EngineUser guideAdd-on managementUpgrading add-onsAdd-on upgrade check
Copy page
Download PDFUpgrading add-ons
Add-on upgrade check
Copy pageDownload PDFAdd-on upgrade check
VKE provides the add-on upgrade check feature. Before an add-on is upgraded, VKE can check key risk points, such as the cluster environment, VKE workload status, and add-on version compatibility. This identifies risks that may cause change failures or business impact in advance and prevents add-ons from being upgraded directly in an abnormal environment.
tip
Supported check scenarios
The add-on upgrade check feature applies to the following common check scenarios. Some check items are defined by the add-ons themselves and evolve with add-on versions.
Check scenario | Scenario description |
Check scenario | Scenario description |
Add-on status check | Verify whether the add-on is in a healthy state and can be upgraded. |
Add-on workload status check | Verify whether all Pods managed by the workloads associated with the add-on, such as Deployments, DaemonSets, and StatefulSets, are running as expected. |
Add-on version consistency check | Verify whether different replicas of the same add-on are running the same version. This prevents issues such as DaemonSet replicas not being upgraded and version mismatches. |
Cluster configurations | Verify whether common environment information meets add-on change requirements, such as cluster configurations and the number of available VPC IPs. |
Custom resource check | Define custom check rules to verify add-on resources that require attention. For example, cloud-controller-manager checks Services, and apmplus-opentelemetry-collector checks its own CRDs. |
Custom checks in business scenarios | Each add-on provides check rules tailored to specific business scenarios, which can be used to access the cluster API server of the user. For example, mgpu checks node resources, and vpc-cni checks incompatible features in ConfigMaps. |
warning
The supported check items vary by add-on. To learn the detailed check items supported by a specific add-on, refer to the release notes of the add-on.
Prerequisites
- The target add-on has no running or pending upgrade check tasks.
- The target add-on has the Upgradable tag.
Procedure
Manually trigger
Automatic trigger
Before upgrading an add-on, you can manually initiate an upgrade check to independently verify whether the current add-on and its cluster meet the upgrade conditions. This operation does not trigger a version change.
- Log in to the VKE console.
- In the left navigation pane, click Cluster. On the page that appears, click the name of the target cluster.
- On the cluster management page, click Addons in the left navigation bar.
- On the Addons page, find the add-on to be upgraded and click ... > Upgrade check.
- In the message that appears, confirm the information about the add-on to be checked and click Confirm.
- You will be redirected to the Add-on upgrade check page. You can refresh the page and wait for the add-on upgrade check to complete.
- After the add-on upgrade check is complete, click View details in the Actions column that corresponds to the add-on to view the add-on upgrade check result.
- If all add-on upgrade check items have passed the check, you can upgrade this add-on. For detailed operations, see Upgrading add-ons.
- If any upgrade check items fail, resolve the issues based on the cause, impact, and remediation suggestions displayed in the console, and then perform the add-on upgrade check again.
-
When you directly upgrade an add-on, the system automatically triggers an add-on upgrade check. For detailed instructions, see Upgrading add-ons.
- Check passed: The system continues the add-on upgrade, and you can track the upgrade progress in the add-on change records.
- Check failed: The system stops this upgrade, and the add-on remains at its pre-upgrade version and state. You can view the cause of the failure in the upgrade check records and resolve the issue by following the remediation suggestions provided by the system.
tip
To improve the success rate of add-on upgrades, we recommend first manually triggering an upgrade check, reviewing any failed check items, and resolving the issues in advance.
What to do next
VKE enables you to view upgrade check records. Upgrade check records provide a history of previous add-on upgrade checks, helping you troubleshoot check failures and confirm the resolution status of check items.
- In the left navigation bar of the cluster management page, click Addons.
- In the upper-right corner of the Addons page, click Check log for add-on upgrades.
- View previous check tasks in the record list. You can filter check records by add-on name.
- In the Actions column that corresponds to the target add-on, click View details to view check details.
- If the Pending tab on the Check details page contains failed check items or items that require attention, promptly resolve the issues by following the remediation suggestions.
Last updated: 2026.09.24 15:22:31
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
