-
Notifications
You must be signed in to change notification settings - Fork 114
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
Check status changes for externally managed interface - netdev device type #632
Comments
Hi @mlguerrero12 thanks for the issue! So the idea why we don't want to do it in the sriov-cni is from security point of view. |
This sets netdevice as default in the CRD to not depend on the mutating webhook. Fixes k8snetworkplumbingwg/sriov-network-operator#632 Signed-off-by: Marcelo Guerrero <[email protected]>
This sets netdevice as default in the CRD to not depend on the mutating webhook. Fixes k8snetworkplumbingwg/sriov-network-operator#632 Signed-off-by: Marcelo Guerrero <[email protected]>
follow-up of #530
NeedToUpdateSriov
always returns true for externally managed interfaces with netdev device type. This causes a loop in the check status logic.As per the comment, we always return true to be sure the admin mac address is configured as expected. Why do we need to do this? is it not overwritten when mac is set in the sriov-cni config. Can we not do this operation in the cni instead?
Additionally,
NeedToUpdateSriov
shouldn't check mtu or numVfs changes for externally managed interfaces. At least, it will avoid draining the node when the device type is a dpdk one.c.c. @SchSeba
The text was updated successfully, but these errors were encountered: