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 EngineWhat's NewProduct Announcement[Product announcement] NGINX Ingress EOM
Copy page
Download PDFProduct Announcement
[Product announcement] NGINX Ingress EOM
Copy pageDownload PDF[Product announcement] NGINX Ingress EOM
Change
Kubernetes SIG Network and the Security Response Committee announced the retirement of Ingress NGINX in the community blog Ingress NGINX Retirement: What You Need to Know. To align with the community changes, VKE adjusted its maintenance policy for the NGINX Ingress Controller add-on:
- Limited maintenance stage: From now until November 30, 2026, VKE will provide minimal maintenance required to address only a very limited number of critical security issues (depending on available maintenance resources).
- Official retirement time: Starting from December 1, 2026, VKE will fully discontinue all maintenance efforts, including but not limited to:
- No longer releasing new versions or feature iterations.
- No longer fixing any known or newly discovered vulnerabilities.
- No longer providing security patches or compliance updates.
- Switching the GitHub code repository to read-only mode.
Impact
VKE plans to stop support for the NGINX Ingress Controller starting from December 1, 2026, Beijing Time (UTC+8). The following cluster features will be affected by this support change:
Features affected | Change | Reference |
Features affected | Change | Reference |
cluster | The ingress-nginx add-on will no longer be available during cluster creation. | |
Ingresses | Creation of NGINX Ingresses is no longer supported. | |
Add-on management | The ingress-nginx add-on can no longer be installed in clusters. | |
Application templates | The ingress-nginx entry in the application templates will be retained. You can still use the application templates to install resources in a cluster. However, the VKE team will no longer provide security and reliability maintenance for template resources. Use these application templates with caution. |
warning
The discontinuation of the feature and add-on will have slightly different impacts on new and existing users:
- For new users: We recommend using APIG Ingress or ALB Ingress. If you continue using NGINX Ingress, fully understand the associated risks before contacting your account manager.
- For existing users: Existing deployments and capabilities in clusters with the ingress-nginx component installed or NGINX Ingress resources created continue functioning normally. However, we recommend prompt migration to avoid potential usage risks.
Migration solutions
To ensure security of cluster-based applications, we recommend migrating existing NGINX Ingress workloads to other types of Ingresses before the retirement of the NGINX Ingress Controller. For details, see the following documentation:
Plan your Ingress migration based on your business scenarios. If you encounter any issues during migration or need more technical support, feel free to submit a ticket.
Last updated: 2026.06.02 10:52:59
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
