-
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
kpr: ensure DirectRoutingDevice is in devices #14054
Conversation
eeed717
to
bc10e19
Compare
Set to draft because it's untested. |
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.
Thanks for debugging and fixing.
According to the docs:
If the direct routing device does not exist within devices, Cilium will add the device to the latter list.
So I guess instead of panicking we should just add the direct routing device to the devices list.
8f512e2
to
ca0b36d
Compare
modified the patch to do so. |
ca0b36d
to
6b1c588
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.
LGTM. Non-blocking comment.
ff3d86a
to
11d410c
Compare
Commit 31c19b105e96cfffe0e129896461bb21eac0534c does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
As reported by #14052, there can be a panic if the configured DirectRoutingDevice is not included in devices. (InitNodePortAddrs() is called with option.Config.Devices.) docs state that: If the direct routing device does not exist within devices, Cilium will add the device to the latter list. so this patch adds the device to the list. Fixes #14052 Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com> Co-authored-by: Martynas Pumputis <m@lambda.lt>
31c19b1
to
17e6123
Compare
test-me-please |
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.
Thanks!
retest-runtime |
(runtime test failed because it could not provision a VM) |
As reported by #14052, there can be a panic if the congfigured
DirectRoutingDevice is not included in devices. (InitNodePortAddrs() is
called with option.Config.Devices.)
Fix this by checking that the specified is included and fail otherwisesince this is probably a user error.
docs state that:
If the direct routing device does not exist within devices, Cilium
will add the device to the latter list.
so this patch adds the device to the list.
Fixes #14052
Signed-off-by: Kornilios Kourtis kornilios@isovalent.com