-
Notifications
You must be signed in to change notification settings - Fork 19
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
Remove driver version check #37
Remove driver version check #37
Conversation
Signed-off-by: Andrea Panattoni <[email protected]>
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.
just a small nit and we can merge this one
README.md
Outdated
@@ -9,7 +9,10 @@ The SR-IOV Network Metrics Exporter is designed with the Kubernetes SR-IOV stack | |||
The sysfs collector for Virtual Function telemetry supports NICs with drivers that implement the SR-IOV sysfs management interface e.g. ice, i40e, mlnx_en and mlnx_ofed. | |||
|
|||
The netlink collector relies on driver support and a kernel version of 4.4 or higher. | |||
To support netlink, we recommend these driver versions: an i40e driver of 2.11+ or higher for Intel® 700 series NICs and ice driver 1.2+ for Intel® 800 series NICs. | |||
To support netlink, we recommend these driver versions: |
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.
maybe something about minimal supported driver version or something like that?
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.
I rephrased as:
The netlink collector relies on driver support and a kernel version of 4.4 or higher.
Also, the following minimum driver versions are required for this collector:
- `i40e` - 2.11+ for Intel® 700 series NICs
- `ice` - 1.2+ for Intel® 800 series NICs
- `mlx5_core` - 5.15+ for Mellanox NICs
does it sound better?
12efd05
to
224ef7e
Compare
Avoid checking the driver version against a user defined map. If the netlink collector is not supported by the Physical Function, the next provided collector (e.g. `sysfs`) is used. Signed-off-by: Andrea Panattoni <[email protected]>
@Eoghan1232 please take a look at this |
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.
I very much like this approach!
Makes changes down the line easier too, without the hassle of driver validation due to so many variations of namings.
LGTM!
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
nice work!
sriov-network-metrics-exporter
k8snetworkplumbingwg/sriov-network-operator#655
As a leftover of: - Remove driver version check k8snetworkplumbingwg#37 the daemonset deployment file must be updated removing related references. Signed-off-by: Andrea Panattoni <[email protected]>
As a leftover of: - Remove driver version check #37 the daemonset deployment file must be updated removing related references. Signed-off-by: Andrea Panattoni <[email protected]>
Avoid checking the driver version against a user
defined map. If the netlink collector is not supported by
the Physical Function, the next provided collector (e.g.
sysfs
)is used.
superseeds:
drivers.yaml
file optional #35cc @Eoghan1232 , @SchSeba