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 guideNetworkingIngressNginx IngressConfiguring consistent hashing for load balancing with NGINX Ingresses
Copy page
Download PDFNginx Ingress
Configuring consistent hashing for load balancing with NGINX Ingresses
Copy pageDownload PDFConfiguring consistent hashing for load balancing with NGINX Ingresses
Nginx Ingresses support consistent hashing, which can effectively resolve load balancing instability caused by dynamically adding or removing backend servers. This topic describes how to configure consistent hashing for NGINX Ingresses.
warning
NGINX Ingress support will soon be discontinued. For details, see [Product announcement] NGINX Ingress EOM.
Background information
The source IP Hash method supported by NGINX Ingresses by default uses a linear hash space. The system selects the target backend server based on the hash value computed from the source IP address. This ensures that the same source IP is always routed to the same backend server.
However, this approach has an issue: when backend servers are added or removed, all source IPs must undergo re-hashing to adapt and reroute to the changed number of backend servers. This results in massive session disruption or cache invalidation.
To address the above issue, NGINX Ingresses introduce a consistent hashing algorithm. This algorithm replaces the conventional linear hash space with a ring-based hash space. When backend servers are added or removed, only a small portion of data (specifically, the segment adjacent to the added or removed server) requires rerouting. This approach effectively resolves load balancing disruption caused by dynamic scaling of backend servers.
Prerequisites
- The cluster has been connected. For more details, see Connecting to clusters.
- Installed ingress-nginx add-on. For details, see Installing add-ons.
Procedure
Nginx Ingresses support consistent hashing for load balancing using annotations. The following file provides an example of NGINX Ingress configuration:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx-ingress # Ingress name
annotations:
nginx.ingress.kubernetes.io/upstream-hash-by: "$request_uri"
spec:
ingressClassName: nginx # Specify an Ingress controller.
rules:
- host: example.com # The domain name in the forwarding rule.
http:
paths:
- backend:
service:
name: service-demo # The name of the service where requests are forwarded.
port:
number: 80 # The port that the service opens to receive forwarded requests.
path: / # The access path.
pathType: ImplementationSpecific
The following table describes the annotations.
Key | Type | Required | Description | default value |
Key | Type | Required | Description | default value |
nginx.ingress.kubernetes.io/upstream-hash-by | String | Yes | The consistent hashing rule. It supports NGINX parameters, text values, or any combination of the two. Examples:
| No |
tip
Last updated: 2026.07.24 14:51:37
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
