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 URL rewrite rules in Nginx Ingresses
Copy page
Download PDFNginx Ingress
Configuring URL rewrite rules in Nginx Ingresses
Copy pageDownload PDFConfiguring URL rewrite rules in Nginx Ingresses
Nginx Ingress can rewrite request URLs. This topic introduces how to configure the URL rewrite feature of Nginx Ingress.
warning
NGINX Ingress support will soon be discontinued. For details, see [Product announcement] NGINX Ingress EOM.
Background information
In certain application scenarios, the path in a back-end service URL can differ from the one configured in the corresponding NGINX Ingress. By default, Nginx Ingress forwards traffic to backend services running at the same URL as the requests. If you do not create URL rewrite rules, your requests to those applications will receive 404 responses. Therefore, you need to rewrite URLs by configuring rules to ensure requests can reach the expected destinations.
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
An NGINX Ingress supports configuring URL rewriting based on annotations. The following YAML file provides an example.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx-ingress # Ingress name
annotations:
nginx.ingress.kubernetes.io/rewrite-target: "/$2"
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: /demo(/|$)(.*) # 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/rewrite-target | String | Yes | The target URI for URL rewriting. It uses regular expressions to define capture groups. | No |
In the nginx.ingress.kubernetes.io/rewrite-target annotation, you can use regular expressions to define capture groups. For example, in the sample file above, $2 means that all characters matched in the second pair of parentheses (.*) in the path field are inserted as the value of the nginx.ingress.kubernetes.io/rewrite-target annotation. For example:
- Request to example.com/demo will be rewritten to example.com/
- Requests to example.com/demo/ will be rewritten to example.com/
- Requests to example.com/demo/test will be rewritten as example.com/test
Validating results
Viewing configuration
Run the following command to view the Ingress configuration.
kubectl get ingress
If the response is similar to the following one, the Ingress has been created. The address 180.xxx.xxx.xxx is the public or private IP of the CLB configured for the Nginx Ingress.
NAME CLASS HOSTS ADDRESS PORTS AGE
nginx-ingress nginx example.com 180.xxx.xxx.xxx 80 74s
Testing the connections to services
The default path of the back-end service is /, while the path configured in the Ingress is /demo. If URL rewrite rules are not configured, a 404 response is returned because the request path does not exist.
curl -H "Host: example.com" http://180.xxx.xxx.xxx/demo
The expected response is as follows:
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
With this URL rewriting configured, use the following command to access the service.
curl -H "Host: example.com" https://180.xxx.xxx.xxx/demo
If the following response is returned, the back-end service is accessible.
<!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>
Last updated: 2026.07.24 14:51:37
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
