-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Populates backend map from V2 backend map #17308
Conversation
9a77289
to
a0ca618
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this pull request should only be opened against v1.10 given we won't need this code in v1.11.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, a few nits. Also, I think backporters would appreciate if you could provide more context in the commit msg / PR description why this needs to be backported to v1.10.
test-me-please Job 'Cilium-PR-K8s-1.16-net-next' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
Travis seems to hit a github infra flakiness (connection timed out while checking out env). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did another round of reviewing. A few things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, getting closer to ready :-) Last comment about DRY.
This is potentially a lossy process, ideally we copy everything from v2 map to v1 map but since v1 map's key type is smaller (16b vs 32b in v2), for entries with an ID that is larger than 64k, we drop them. This means existing connection could potentially be interrupted when downgrading from v2 to v1. This logic needs to go into 1.10 releases, because we will introduce v2 map in 1.11 and the downgrade logic needs to be in place. Signed-off-by: Weilong Cui <cuiwl@google.com>
test-backport-v1.10 |
test-backport-1.10 |
Hit flake: #17365 |
Only test failure is a known flake tracked in cilium/cilium-cli#367, not related to change. |
This is a lossy process, we copy everything from v2 map to v1 map but
since v1 map's key type is smaller (16b vs 32b in v2), for entries with
and ID that is larger than 64k, we drop them. This means existing
connection could potentially be interrupted when downgrading from v2 to
v1.
V2 map introduced in #17235, this is the downgrade path.
Signed-off-by: Weilong Cui cuiwl@google.com
Fixes: #17262