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 guideNetworkingIngressALB IngressCustomize ALB Ingress forwarding rulesConfiguring traffic forwarding to multiple back-end services
Copy page
Download PDFCustomize ALB Ingress forwarding rules
Configuring traffic forwarding to multiple back-end services
Copy pageDownload PDFConfiguring traffic forwarding to multiple back-end services
An ALB Ingress lets you configure multiple backend server groups in a forwarding rule and use either Services in the cluster or existing backend server groups. When a request passes through the ALB instance, the ALB instance can forward it to different back-end server groups based on weights.
warning
It is highly recommended that you first read Considerations for using ALB Ingresses carefully before getting started.
Prerequisites
- The cluster has been connected. For details, see Connecting to clusters.
- An ALB instance has been created. For details, see Creating ALB Ingresses by using kubectl.
- The alb-ingress-controller add-on has been installed and upgraded to v0.35.0 or later. For details, see Upgrading add-ons.
Procedure
Creating through the console
tip
You can only use the console to configure an ALB ingress that uses a Standard edition ALB instance. To use a Basic edition ALB instance, see the following YAML configuration.
- Log in to the VKE console.
- In the left navigation bar, click Cluster.
- On the cluster list page, click the target cluster for which you need to configure an Ingress.
- In the left navigation bar of the cluster management page, click Services and Ingresses > Ingress. On the page that appears, click Create Ingress.
- Select Application Load Balancer (ALB) for Ingress type.
- Enable Custom forwarding rules and configure the details of the forwarding rules.
Parameter | Description |
Parameter | Description |
Forwarding conditions | Configure forwarding conditions, including the domain name, path, and HTTP header.
|
Forwarding actions | The target service and port for forwarding. For this example, select the Forward to action.
tip When you configure multiple services, the sum of their weights is not required to be 100. The ALB instance can forward client traffic to the corresponding service by proportion based on the weight of each service. For details, see Server group weighting. |
- Click Confirm.
Creating through kubectl
You can specify multiple back-end server groups for an ALB Ingress by using annotations. The configuration slightly varies based on whether the ALB Ingress uses a Standard edition ALB instance or a Basic edition ALB instance.
Standard edition ALB
Basic edition ALB
The following content provides sample configurations and annotation descriptions for an ALB Ingress that uses a Standard ALB instance.
Warning
The {{service-name}} field in the annotation must match the name of the back-end service configured in spec.rules. For example, in this case, the correct annotation is ingress.vke.volcengine.com/loadbalancer-actions.service-demo.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: alb-ingress # The custom Ingress name.
namespace: default # Namespace of the Ingress
annotations:
ingress.vke.volcengine.com/loadbalancer-actions.{{service-name}}: |
[{
"type": "ForwardGroup",
"forwardGroupConfig": {
"serverGroupStickySession": {
"enabled": "on",
"timeout": 100
},
"backends": [
{
"serviceName": "service-demo-a",
"weight": 80,
"servicePort": 80
},
{
"serviceName": "service-demo-b",
"weight": 20,
"servicePort": 80
}
]
}
}]
spec:
ingressClassName: alb
rules:
- host: example.com
http:
paths:
- pathType: Prefix
path: /
backend:
service:
name: service-demo # The service name. The name needs to be consistent with the value of {{service-name}} in the loadbalancer-actions.{{service-name}} annotation.
port:
name: use-annotation # The fixed value. When you configure multiple back-end server groups, port.name must be use-annotation.
The following table describes fields in the ingress.vke.volcengine.com/loadbalancer-actions.{{service-name}} annotation.
Parameter | Type | Description | Default value |
Parameter | Type | Description | Default value |
type | String | The action type of the custom forwarding rule. If you want to forward traffic to multiple back-end server groups, you need to set the value to ForwardGroup. | No |
forwardGroupConfig | Object of StickySessionConfig | The configuration of session persistence between back-end server groups. | No |
backends | Array of BackendConfig | The configurations of the back-end servers. | No |
StickySessionConfig
Parameter | Type | Description | default value |
Parameter | Type | Description | default value |
serverGroupStickySession.enabled | String | Whether to enable the session persistence feature between back-end service groups. Valid values:
| off |
serverGroupStickySession.timeout | Integer | Configure the session persistence timeout between back-end server groups.
| 1000 |
BackendConfig
Parameter | Type | Description | Default value |
Parameter | Type | Description | Default value |
serviceName | String | The name of the back-end service. If no service is available, create a service based on the instructions in Services. | No |
weight | Integer | The weight of the back-end service. Valid values: 0 to 100.
tip When you configure multiple services, the sum of their weights is not required to be 100. The ALB instance can forward client traffic to the corresponding service by proportion based on the weight of each service. For details, see Server group weighting. | No |
servicePort | Integer | The port number of the back-end service. The value can range from 1 to 65535. | No |
You can specify multiple back-end server groups for an ALB Ingress by using annotations. Supported back-end server groups can be services within the cluster and existing back-end server groups (identified by ID) on the ALB instance. The following is an example YAML with comments for annotations.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: alb-ingress # The custom Ingress name.
namespace: default # Namespace of the Ingress
annotations:
ingress.vke.volcengine.com/loadbalancer-rules-configs-forward: |
[
{
"host": "example.com",
"path": "/",
"serverGroups" : [{
"serviceName": "service-demo-a",
"weight": 80,
"servicePort": 80
},
{
"serverGroupId": "rsp-1ij9jfh***",
"weight": 30
},
{
"serviceName": "service-demo-b",
"weight": 20,
"servicePort": 80
}]
}
]
spec:
ingressClassName: alb # The name of the ALB instance.
rules:
- host: example.com
http:
paths:
- pathType: Prefix
path: / # The matching path for the request.
backend:
service:
name: forward # The service name. This field has a fixed value of forward, which indicates that traffic is forwarded according to the annotation configuration.
port:
name: use-annotation # The port name. This field has a fixed value of use-annotation, which indicates that traffic is forwarded according to the annotation configuration.
The following table explains fields in ingress.vke.volcengine.com/loadbalancer-rules-config-forwad.
Parameters | Type | Description | default value |
Parameters | Type | Description | default value |
host | String | The domain in the forwarding rule. | No |
path | String | The path in the forwarding rule. | No |
serverGroups | Array of serverGroupConfig | The back-end server groups for the ALB Ingress. You can specify up to five back-end server groups for an ALB Ingress. | No |
stickySessionEnabled | Boolean | Whether to enable session persistence across groups. Valid values:
| false |
stickySessionCookieTimeout | Integer | Session persistence timeout between server groups. The timeout is in seconds. The value range is 1 to 86400. | 1000 |
serverGroupConfig
Parameter | Type | Description | default value |
Parameter | Type | Description | default value |
serviceName | String | The name of the service in the cluster. tip If you configure this field, you must also configure the servicePort field. | No |
servicePort | Integer | Service port number. The valid range is 1 to 65535. | 80 (HTTP) 443 (HTTPS) |
serverGroupID | String | The ID of an existing back-end server group. tip This field and the serviceName field cannot be present at the same time. | No |
weight | Integer | Weight for the back-end server group. The valid range is 0 to 100.
tip | No |
Validating results
Viewing configuration
tip
The details pages of forwarding rules differ between Standard edition ALB instances and Basic edition ALB instances. This topic provides an example of viewing the details page of a forwarding rule for a Standard edition ALB instance.
- Log in to the ALB console.
- Click Instance in the left navigation bar. In the instance list, find the target ALB instance and click Listener in the Actions column.
- On the listener details page, find the target listener. In the Actions column, click Edit forwarding rules to view the existing forwarding rules of the listener. You can see multiple back-end server groups. The rule details should be consistent with the configured ones.
- For a forwarding rule, click
to view rule details. The rule details should be consistent with the configured ones.
Sending access requests for verification
tip
Before verification, make sure that you have deployed back-end applications and services in the cluster. In this example, an Nginx image is used and the service path is /. For deployment steps, see Using ALB Ingresses for service deployment.
Access the service by using the domain name configured in the ALB Ingress. In this example, 14.***.***.*** is the public IP address of the ALB instance.
curl -H "Host: example.com" http://14.***.***.***
The expected result is as follows: When the requested domain is example.com and the original path is /, the service is accessible through the ALB Ingress.
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
You specified multiple back-end server groups for the ALB Ingress, and configured different services and weights for each back-end server group. If you access the service multiple times, traffic is forwarded to different back-end server groups according to the weight ratio. For example, execute the following command to send 20 access requests:
for i in {1..20}; do curl -H "Host: example.com" http://14.***.***.***; done;
The expected result is that traffic is forwarded to different back-end server groups according to the weights specified in the configuration.
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
This is the old version of nginx
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
This is the old version of nginx
This is the new version of nginx
This is the old version of nginx
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
This is the old version of nginx
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
This is the new version of nginx
Last updated: 2026.10.16 16:55:40
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
