Adrian Chiris

image is here: https://github.com/Mellanox/k8s-rdma-shared-dev-plugin/pkgs/container/k8s-rdma-shared-dev-plugin

a few comments on why we might not want this: 1. you can disable actions on fork 2. actions run against master and v* tags, on a normal dev flow...

closing this PR then.

#305 solves the issue.

Can use goReleaser GithubAction to automate this. https://goreleaser.com/ci/actions/

Are there implications of keeping the interface name in results empty ? is that OK from[ CNI spec](https://github.com/containernetworking/cni/blob/master/SPEC.md#success) POV? One thing i can think of is that we rely on...

+1 for the **Proposed behavior** hopefully for DPU we will be able to load configuration by mstfwreset+reboot and save the powercycle then we can remove this check from the mellanox...

>GetDevices(): error creating new device: "error getting driver info for device 0000:3b:0a.0 readlink /sys/bus/pci/devices/0000:3b:0a.0/driver: no such file or directory" are the created SR-IOV virtual functions bound to intel driver ?...

@e0ne can you rebase the pr ?

> in general another point we need to take care here is when we create/update a pool it will not do anything we need to wait for the nodePolicy controller...