Remove podman network causing outbound latency #3865
Merged
Conversation
This file contains 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
bennerv
requested review from
jewzaam,
hawkowl,
rogbas,
petrkotas,
jharrington22,
cblecker,
cadenmarchese,
UlrichSchlueter,
SudoBrendan,
yjst2012,
jaitaiwan,
anshulvermapatel,
hlipsig,
tiguelu,
SrinivasAtmakuri,
mociarain,
kimorris27,
tsatam and
bitoku
as code owners
bennerv
force-pushed
the
bvesel/podman-network-hotfix
branch
from
15aea7f to
3a0e6bb
Compare
|
untested as it requires a full-dev env. |
|
PR no longer needed. Closing out. |
|
/azp run ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
e2e isn't testable by these scripts. Running CI but everything was good. Again these script changes are untested. |
SrinivasAtmakuri
added
bug
tsatam
approved these changes
Sep 26, 2024
tsatam
pushed a commit
that referenced
this pull request
Sep 26, 2024
slawande2
pushed a commit
that referenced
this pull request
Sep 27, 2024
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.
Which issue this PR addresses:
Fixes a latency issue with outbound connections caused by the creation of dedicated podman networks.
What this PR does / why we need it:
Fix a regression in outbound connection latency.
Test plan for issue:
RP deploy
Is there any documentation that needs to be updated for this PR?
How do you know this will function as expected in production?