[v3.31] eBPF: fix that local workload with borrowed IPs lose connectivity #11654
+78
−10
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
…ojectcalico#11640) eBPF: fix that local workload with borrowed IPs lose connectivity The old condition checked that the "borrowed" flag was false before checking if the route was a workload. There's no reason that a local workload can't have a borrowed IP, so this was a bug. We now have an explicit "really a local WEP" flag; use that explicitly to avoid confusion with the informational flags (where multiple flags can be set for borrowed IPs). (cherry picked from commit c3ae458)
fasaxc
added
release-note-required
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry-pick history
Description
The old condition checked that the "borrowed" flag was false before checking if the route was a workload. There's no reason that a local workload can't have a borrowed IP, so this was a bug.
We now have an explicit "really a local WEP" flag; use that explicitly to avoid confusion with the informational flags (where multiple flags can be set for borrowed IPs).
Related issues/PRs
CORE-12198
Release Note