mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2025-03-05 08:17:04 +00:00
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. |
||
---|---|---|
.. | ||
cpuid_rule.go | ||
kconfig_rule.go | ||
loaded_kmod_rule.go | ||
nodename_rule.go | ||
pci_id_rule.go | ||
usb_id_rule.go |