From c1d541c783dcf30e1f97c76f66eebcfa536027ea Mon Sep 17 00:00:00 2001 From: Qiu Jian Date: Thu, 1 Feb 2018 18:46:25 +0800 Subject: [PATCH] Add document for connection-proxy-header annotation (#2014) --- docs/user-guide/annotations.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/user-guide/annotations.md b/docs/user-guide/annotations.md index 3dcbbc171..5a5d72820 100644 --- a/docs/user-guide/annotations.md +++ b/docs/user-guide/annotations.md @@ -60,6 +60,7 @@ The following annotations are supported: |[nginx.ingress.kubernetes.io/whitelist-source-range](#whitelist-source-range)|CIDR| |[nginx.ingress.kubernetes.io/proxy-buffering](#proxy-buffering)|string| |[nginx.ingress.kubernetes.io/ssl-ciphers](#ssl-ciphers)|string| +|[nginx.ingress.kubernetes.io/connection-proxy-header](#connection-proxy-header)|string| **Note:** all the values must be a string. In case of booleans or number it must be quoted. @@ -430,3 +431,10 @@ Using this annotation will set the `ssl_ciphers` directive at the server level. ```yaml nginx.ingress.kubernetes.io/ssl-ciphers: "ALL:!aNULL:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP" ``` + +### Connection proxy header +Using this annotation will override the default connection header set by nginx. To use custom values in an Ingress rule, define the annotation: + +```yaml +nginx.ingress.kubernetes.io/connection-proxy-header: "keep-alive" +```