public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Ingress TLS configuration documentation for NGINX v0.22

Browse Source 
The documentation has been revised to provide clearer guidance on
configuring Ingress for external TLS with NGINX v0.22. Key changes
include:

- Removed references to NGINX v0.25.
- Added instructions for enabling the `use-forwarded-headers`
  option in the `cluster.yml` for RKE installations.
- Included steps for creating a custom
  `rke2-ingress-nginx-config.yaml` for RKE2 installations.
- Provided a YAML snippet for HelmChartConfig to demonstrate
  how to set the `use-forwarded-headers` option in Helm chart
  values.
This commit is contained in:
John Carew
2025-06-05 13:34:10 -05:00
parent cb46b1030b
commit e73b7efaef
7 changed files with 115 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md
+1 -1
View File
@@ -212,7 +212,7 @@ If you are using a Private CA signed certificate (or if `agent-tls-mode` is set
Your load balancer must support long lived websocket connections and will need to insert proxy headers so Rancher can route links correctly.
### Configuring Ingress for External TLS when Using NGINX v0.25
### Configuring Ingress for External TLS when Using NGINX v0.22
In NGINX v0.22, the behavior of NGINX has [changed](https://github.com/kubernetes/ingress-nginx/blob/06efac9f0b6f8f84b553f58ccecf79dc42c75cc6/Changelog.md) regarding forwarding headers and external TLS termination. Therefore, in the scenario that you are using external TLS termination configuration with NGINX v0.22, you must enable the `use-forwarded-headers` option for ingress: