mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2025-03-05 16:27:05 +00:00
6f881a4822
Stop converting "=y" and "=m" to "true" for the raw feature values used
in "kernel.config" custom rule processing.
In practice, this means that to check if a kernel config flag has been
set to "y" or "m", one needs to explicitly check for both of the values:
matchFeatures:
- feature: kernel.config
matchExpressions:
FOO: {op: In, value: ["y", "m"]}
instead of (how it used to be):
matchFeatures:
- feature: kernel.config
matchExpressions:
FOO: {op: IsTrue}
The legacy kconfig custom rule is unchanged as are the
kernel-config.<flag> feature labels.
|
||
|---|---|---|
| .. | ||
| cpu | ||
| custom | ||
| fake | ||
| iommu | ||
| kernel | ||
| local | ||
| memory | ||
| network | ||
| pci | ||
| storage | ||
| system | ||
| usb | ||
| config.go | ||
| mock_LabelSource.go | ||
| source.go | ||
| source_test.go | ||