Adrian Chiris

was an issue filed against topology manager ? maybe the algorithm can be improved

I would say there are cases that need to be handled: 1. node state has changed (driver bound, sriov created) that caused change to a resource 2. config map changed...

@amorenoz can you elaborate ? you mean keep the IDs of existing devices?

I understand your point. But should it be the device plugin responsibility to handle that ? You will essentially end up the same if you do the changes and restart...

> For Intel NICs (X700 & E800 series) right now, you would have to reset the VF number to zero, and then set it to your desired amount - therefore...

adding a kubectl plugin would definetly be nice IMO ! regarding the rescan, i think sriov dp should be reactive (to some extent) to both the system state and config...

This has been discussed in today's community meeting. - agreement that supporting system resource updates and sriov network device plugin config updates are two different topics that should be addressed...

This was discussed in K8s NPWG network & resource mgmt meeting on 08.10.2021. this enhancement proposal is approved. documentation should be added as well, explaining the nature of the stable...

We have it for other Arch, so im fine with making things consistent and having one for `amd64` as well. While we are at it, should ${GitHub tag} image be...

This was discussed in K8s NPWG network & resource mgmt meeting on 08.10.2021. this enhancement proposal is approved.