v3.3: New features and bug fixes

Project has moved from Intel to Network Plumbing Working Group with new URL https://github.com/k8snetworkplumbingwg/sriov-network-device-plugin

New Features:

• Allow configuration per node instead of per k8 cluster #279
• Support for running within a VM with no iommu support #272
• Add rootDevices selector for netDevice #264
• Include contribution guide #150
• Improve RDMA logging #226
• Add VF creation dependency docs before starting DP #244
• Update NVidia VF setup instructions #252
• Ability to share /dev/vhost-net #228
• Include ARM64 daemonset #227
• Add pciAddress selector #195
• Add go mod support #225

Bug fixes:

• Receive termination signal correctly #284
• Fix help output #296
• Fix overlapping pf names causing false matches #263
• Fix golang/x/text dependency CVE #254
• Change image pull policy from never to IfNotPresent so user doesn't need to manually pull #243
• Skip devices that do not have PF names when "pfNames" selector is used #235
• Clean go modules correctly #233

v3.2

• Add support to pfNames selector with VF range and list (#193)
• Configurable resource prefix per resource pools (#194)
• Add ddp selector (#199)

Released version v3.1

Features:

• Add K8s topology manager support to report NUMA node info of devices
• Update deployments to support k8s v1.16 api
• Allow device to be added without PF info (for VM use-cases)
• New selector based on PF name + VF index range
• Only exclude interfaces with default route entry
• Updated docs to add DANM support
• Add LinkType selector("ether", "infiniband")
• Add resource-prefix parameter in entrypoint.sh

Fix:

• fix: issue with igb_uio not exporting device files
• fix: a runtime error if PF interface not found

Released version v3.0.0

• "Selectors" based dynamic device discovery and grouping
• Filtering the resources by the PF device name
• RDMA mode support
• Kubelet plugin watcher mode

Released version 2.0.0

• Added support for multiple resource endpoints (#26)
• New scheme for exported env variable names
• Publish docker image on dockerhub