-
Notifications
You must be signed in to change notification settings - Fork 14
Add reverse-proxy troubleshooting section to Kubernetes docs #98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Philipp Scheit <[email protected]>
Co-authored-by: Philipp Scheit <[email protected]>
stevenrombauts
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the last changes make things a little less clear, if you're not using Nginx as reverse proxy. It's a little bit confusing because the entire text now assumes you do, until the last sentence.
What confused me was the mention of proxy_pass in the third paragraph, if we can just make it clear that this is a nginx-specific directive, then everything sounds much more clearer to me. What do you think?
|
please send another pr to update the docs reference |
|
@pscheit Thanks for the hint about updating the docs reference, that would have certainly slipped my mind 🙂 |
Will look like this:

I also mentioned another possible issue if they are using different hostnames on their internal network for the upstream just to be sure.