docs: add steps for configuring trusted headers & origins in Helm chart #8031
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Do we need to add those to our reverse proxy docs? |
bpmct
approved these changes
Jun 14, 2023
|
Thoughts on adding a header to so this section is easy to reference in email/Slack links? |
@matifali i don't think so. the variables are used more in cloud load balancing context. |
deansheather
approved these changes
Jun 14, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this PR documents steps for setting the
X-Forwarded-Forheader and trusted proxy origins in the Helm chart. our v1 Helm chart supports this natively.a customer struggled to find documentation on this, as they were looking to preserve the client IP in the audit logs while maintaining a
ClusterlevelexternalTrafficPolicy.