mirrors/node-feature-discovery
mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-30 19:54:46 +00:00
Code Activity

Merge pull request #1076 from Sajiyah-Salat/sajiyah-#1075

Browse source 
Update worker-configuration-reference.md
This commit is contained in:
Kubernetes Prow Robot 2023-03-09 13:06:30 -08:00 • committed by GitHub
commit fb69bac17f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/reference/worker-configuration-reference.md
View file

@ -355,15 +355,15 @@ sources:
hooksEnabled: true # true by default hooksEnabled: true # true by default
``` ```
### soures.pci ### sources.pci
#### soures.pci.deviceClassWhitelist #### sources.pci.deviceClassWhitelist
List of PCI [device class](https://pci-ids.ucw.cz/read/PD) IDs for which to List of PCI [device class](https://pci-ids.ucw.cz/read/PD) IDs for which to
publish a label. Can be specified as a main class only (e.g. `03`) or full publish a label. Can be specified as a main class only (e.g. `03`) or full
class-subclass combination (e.g. `0300`) - the former implies that all class-subclass combination (e.g. `0300`) - the former implies that all
subclasses are accepted. The format of the labels can be further configured subclasses are accepted. The format of the labels can be further configured
with [deviceLabelFields](#soures.pci.deviceLabelFields). with [deviceLabelFields](#sources.pci.deviceLabelFields).
Default: `["03", "0b40", "12"]` Default: `["03", "0b40", "12"]`
@ -375,7 +375,7 @@ sources:
deviceClassWhitelist: ["0200", "03"] deviceClassWhitelist: ["0200", "03"]
``` ```
#### soures.pci.deviceLabelFields #### sources.pci.deviceLabelFields
The set of PCI ID fields to use when constructing the name of the feature The set of PCI ID fields to use when constructing the name of the feature
label. Valid fields are `class`, `vendor`, `device`, `subsystem_vendor` and label. Valid fields are `class`, `vendor`, `device`, `subsystem_vendor` and
@ -396,11 +396,11 @@ With the example config above NFD would publish labels like:
### sources.usb ### sources.usb
#### soures.usb.deviceClassWhitelist #### sources.usb.deviceClassWhitelist
List of USB [device class](https://www.usb.org/defined-class-codes) IDs for List of USB [device class](https://www.usb.org/defined-class-codes) IDs for
which to publish a feature label. The format of the labels can be further which to publish a feature label. The format of the labels can be further
configured with [deviceLabelFields](#soures.usb.deviceLabelFields). configured with [deviceLabelFields](#sources.usb.deviceLabelFields).
Default: `["0e", "ef", "fe", "ff"]` Default: `["0e", "ef", "fe", "ff"]`
@ -412,7 +412,7 @@ sources:
deviceClassWhitelist: ["ef", "ff"] deviceClassWhitelist: ["ef", "ff"]
``` ```
#### soures.usb.deviceLabelFields #### sources.usb.deviceLabelFields
The set of USB ID fields from which to compose the name of the feature label. The set of USB ID fields from which to compose the name of the feature label.
Valid fields are `class`, `vendor`, `device` and `serial`. Valid fields are `class`, `vendor`, `device` and `serial`.