Skip to content

Conversation

@IgorBenko
Copy link
Contributor

Will look like this:
ScreenFloat Bildschirmfoto von Google Chrome am 14_11_2024, 16_50_21

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

@IgorBenko IgorBenko requested a review from a team November 14, 2024 15:56
@IgorBenko IgorBenko requested a review from pscheit November 18, 2024 08:00
Copy link
Contributor

@stevenrombauts stevenrombauts left a 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?

@pscheit
Copy link
Contributor

pscheit commented Nov 19, 2024

please send another pr to update the docs reference

@pscheit pscheit merged commit 4164533 into main Nov 19, 2024
@pscheit pscheit deleted the docs/kubernetes-troubleshooting-docs branch November 19, 2024 07:53
@IgorBenko
Copy link
Contributor Author

@pscheit Thanks for the hint about updating the docs reference, that would have certainly slipped my mind 🙂

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.

4 participants