From 6f47e1b750a23a3fc7d06be0085c99bcce74511c Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 28 Oct 2019 11:46:23 -0700 Subject: [PATCH] Remove reference to Rancher in describing NGINX behavior change --- .../en/installation/ha/helm-rancher/chart-options/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/_index.md b/content/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/_index.md index ae722e858c6..ae2bead7b0c 100644 --- a/content/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/_index.md +++ b/content/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/_index.md @@ -158,7 +158,7 @@ Your load balancer must support long lived websocket connections and will need t #### Configuring Ingress for External TLS when Using NGINX v0.25 -Rancher v2.3.0 shipped with NGINX v0.25.1. In this version, the behavior of NGINX has [changed](https://github.com/kubernetes/ingress-nginx/blob/master/Changelog.md#0220) regarding forwarding headers and external TLS termination. Therefore, in the scenario that you are using external TLS termination configuration with NGINX 0.25, you must edit the `cluster.yml` to enable the `use-forwarded-headers` option for ingress: +In NGINX v0.25, the behavior of NGINX has [changed](https://github.com/kubernetes/ingress-nginx/blob/master/Changelog.md#0220) regarding forwarding headers and external TLS termination. Therefore, in the scenario that you are using external TLS termination configuration with NGINX v0.25, you must edit the `cluster.yml` to enable the `use-forwarded-headers` option for ingress: ```yaml ingress: