test: use bridge IP for WireGuard in CI #1648
Open
+29
−18
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
smira
reviewed
Sep 26, 2025
hack/test/integration.sh
Outdated
| LOCAL_IP=$(ip -o route get to 8.8.8.8 | sed -n 's/.*src \([0-9.]\+\).*/\1/p') | ||
|
|
||
| if [[ "${CI:-false}" == "true" ]]; then | ||
| LOCAL_IP=172.20.0.0 |
There was a problem hiding this comment.
Suggested change
| LOCAL_IP=172.20.0.0 | |
| LOCAL_IP=172.20.0.1 |
|
good find! |
utkuozdemir
approved these changes
Sep 26, 2025
Unix4ever
force-pushed
the
use-bridge-ip-wireguard-ci
branch
13 times, most recently
from
7d20541 to
45766cb
Compare
It was using local pod IP which was generating new schematic every time the test runs. Signed-off-by: Artem Chernyshev <[email protected]>
Unix4ever
force-pushed
the
use-bridge-ip-wireguard-ci
branch
from
45766cb to
9c2a094
Compare
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.
It was using local pod IP which was generating new schematic every time the test runs.