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 Nginx Ingress redirect rules
Copy page
Download PDFNginx Ingress
Configuring Nginx Ingress redirect rules
Copy pageDownload PDFConfiguring Nginx Ingress redirect rules
Nginx Ingress can redirect traffic permanently and temporarily, as well as from HTTP to HTTPS. This topic introduces how to configure the Nginx Ingress redirect feature.
warning
NGINX Ingress support will soon be discontinued. For details, see [Product announcement] NGINX Ingress EOM.
Prerequisites
- The cluster has been connected. For more details, see Connecting to clusters.
- Installed ingress-nginx add-on. For details, see Installing add-ons.
Configure permanent redirection
An NGINX Ingress allows you to configure permanent redirection by using an annotation. The following content includes a configuration example and annotation descriptions:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx-ingress # Ingress name
annotations:
nginx.ingress.kubernetes.io/permanent-redirect: "https://www.volcengine.com" # Redirect to the target URL.
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: Prefix # Path type. Available values include Exact (exact match) and Prefix (prefix match).
The following table describes the annotations.
Key | Type | Required | Description | default value |
Key | Type | Required | Description | default value |
nginx.ingress.kubernetes.io/permanent-redirect | String | Yes | The target website address to redirect to. | No |
tip
By default, the status code for a permanent redirect is 301.
Configuring status code for permanent redirect
An NGINX Ingress allows you to configure permanent redirection with the specified HTTP status code by using annotations. The following content includes a configuration example and annotation descriptions:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx-ingress # Ingress name
annotations:
nginx.ingress.kubernetes.io/permanent-redirect: "https://www.volcengine.com" # Redirect to the target URL.
nginx.ingress.kubernetes.io/permanent-redirect-code: "308" # The HTTP status code for the redirection.
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: Prefix # Path type. Available values include Exact (exact match) and Prefix (prefix match).
The following table describes the annotations.
Key | Type | Required | Description | default value |
Key | Type | Required | Description | default value |
nginx.ingress.kubernetes.io/permanent-redirect | String | Yes | Redirect to the specified website. | No |
nginx.ingress.kubernetes.io/permanent-redirect-code | String | Yes | Specify the status code returned when redirecting. Available values: 301 or 308. | No |
Configuring temporary redirection
An NGINX Ingress allows you to configure temporary redirection by using an annotation. The following content includes a configuration example and annotation descriptions:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx-ingress # Ingress name
annotations:
nginx.ingress.kubernetes.io/temporal-redirect: "https://www.volcengine.com" # Redirect to the target URL.
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: Prefix # Path type. Available values include Exact (exact match) and Prefix (prefix match).
The following table describes the annotations.
Key | Type | Required | Description | Default value |
Key | Type | Required | Description | Default value |
nginx.ingress.kubernetes.io/temporal-redirect | String | Yes | Redirect to the specified website. | No |
Configuring redirection from HTTP to HTTPS
An NGINX Ingress allows you to configure redirection from HTTP to HTTPS by using an annotation. The following content includes a configuration example and annotation descriptions:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx-ingress # Ingress name
annotations:
nginx.ingress.kubernetes.io/ssl-redirect: "true" # HTTP redirection to HTTPS.
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: Prefix # Path type. Available values include Exact (exact match) and Prefix (prefix match).
The following table describes the annotations.
Key | Type | Required | Description | default value |
Key | Type | Required | Description | default value |
nginx.ingress.kubernetes.io/ssl-redirect | Boolean | Yes | Whether to redirect HTTP requests to HTTPS. Valid values:
| No |
Validating results
The following command is an example of permanent redirection validation. The address 180.xxx.xxx.xxx is the public or private IP of the CLB configured for the Nginx Ingress.
curl -H "Host: example.com" http://180.xxx.xxx.xxx -I -k
The following is the expected response showing the redirection details.
HTTP/1.1 301 Moved Permanently
Date: Thu, 07 Dec 2023 06:56:48 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://www.volcengine.com
Last updated: 2026.07.24 14:51:37
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
