Skip to content

Commit aa59c53

Browse files
Stonoaledbf
authored andcommitted
Added documentation for Permanent Redirect (#2018)
1 parent a0cefc7 commit aa59c53

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/user-guide/annotations.md

+4
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ The following annotations are supported:
3636
|[nginx.ingress.kubernetes.io/from-to-www-redirect](#redirect-from-to-www)|"true" or "false"|
3737
|[nginx.ingress.kubernetes.io/limit-connections](#rate-limiting)|number|
3838
|[nginx.ingress.kubernetes.io/limit-rps](#rate-limiting)|number|
39+
|[nginx.ingress.kubernetes.io/permanent-redirect](#permanent-redirect)|string|
3940
|[nginx.ingress.kubernetes.io/proxy-body-size](#custom-max-body-size)|string|
4041
|[nginx.ingress.kubernetes.io/proxy-connect-timeout](#custom-timeouts)|number|
4142
|[nginx.ingress.kubernetes.io/proxy-send-timeout](#custom-timeouts)|number|
@@ -324,6 +325,9 @@ The annotation `nginx.ingress.kubernetes.io/limit-rate`, `nginx.ingress.kubernet
324325

325326
To configure this setting globally for all Ingress rules, the `limit-rate-after` and `limit-rate` value may be set in the NGINX ConfigMap. if you set the value in ingress annotation will cover global setting.
326327

328+
### Permanent Redirect
329+
This annotation allows to return a permanent redirect instead of sending data to the upstream. For example `nginx.ingress.kubernetes.io/permanent-redirect: https://www.google.com` would redirect everything to Google.
330+
327331
### SSL Passthrough
328332

329333
The annotation `nginx.ingress.kubernetes.io/ssl-passthrough` allows to configure TLS termination in the pod and not in NGINX.

0 commit comments

Comments
 (0)