Skip to content

Conversation

@linkandzelda91
Copy link

After longer than I would like to admit not understanding why I was getting redirect loops, I stumbled upon this: rancher/rancher#31071

and a second issue requesting the documentation be updated with the discovered solution: rancher/rancher#43875

looks like someone added something for using nginx as an ingress to enable the header pass through, so I pretty much just copied the phrasing. the config I am using is from https://docs.k3s.io/helm#customizing-packaged-components-with-helmchartconfig

I added the other two RFC1918 subnets before realizing there's an allow all option, but I kinda like this a little better because doesn't trust them from WAN addresses.

Fixes #[issue_number]

Reminders

  • See the README for more details on how to work with the Rancher docs.

  • Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

  • If the pull request is dependent on an upcoming release, remember to add a "MERGE ON RELEASE" label and set the proper milestone.

Description

Comments

After longer than I would like to admit not understanding why I was getting redirect loops, I stumbled upon this:
rancher/rancher#31071

and a second issue requesting the documentation be updated with the discovered solution:
rancher/rancher#43875

looks like someone added something for using nginx as an ingress to enable the header pass through, so I pretty much just copied the phrasing. the config I am using is from
https://docs.k3s.io/helm#customizing-packaged-components-with-helmchartconfig

I added the other two RFC1918 subnets before realizing there's an allow all option, but I kinda like this a little better because doesn't trust them from WAN addresses.
Copy link
Contributor

@LucasSaintarbor LucasSaintarbor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@linkandzelda91 Thanks for the PR! Requested some changes and left a question. May you add these changes to the other versions of the docs:

  • versioned_docs/version-2.12/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md
  • versioned_docs/version-2.11/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md
  • versioned_docs/version-2.10/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md
  • versioned_docs/version-2.9/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md

linkandzelda91 and others added 9 commits September 23, 2025 18:53
Clarify ingress configuration requirements for load balancers and NGINX.
Added instructions for configuring Ingress with Traefik for external TLS termination and clarified WebSocket connection requirements.
Updated wording for clarity and added instructions for Traefik configuration.
Added instructions for configuring Ingress with Traefik and clarified WebSocket connection requirements.
Clarified requirements for load balancer and added instructions for Traefik configuration.
@linkandzelda91
Copy link
Author

Added the changes to the other docs after accepting the suggested changes and correcting the noted mistake referencing RKE vs K3s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants