Add configuration to sperate host_ip in extproxy and intproxy connection ip #3290
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
Razz4780
requested changes
Apr 25, 2025
There was a problem hiding this comment.
I think you're changing the wrong thing 👀
Intproxy shoud listen on localhost. The user container and the intproxy sidecar share the same network, so the layer can talk to intproxy.
Don't you want to change the address used by the intproxy when connecting to the extproxy?
…dd-configuration-to-sperate-host_ip-in-extproxy-and
…ost_ip-in-extproxy-and
…ost_ip-in-extproxy-and
…ost_ip-in-extproxy-and
Co-authored-by: Michał Smolarek <[email protected]>
…ost_ip-in-extproxy-and
Razz4780
approved these changes
Apr 28, 2025
DmitryDodzin
deleted the
dimad/mbe-889-add-configuration-to-sperate-host_ip-in-extproxy-and
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.