1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-05 08:17:04 +00:00
node-feature-discovery/source/custom/rules
Markus Lehtonen 6f881a4822 source/kernel: unmangled kconfig values for custom rules
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.
2021-12-02 10:06:21 +02:00
..
cpuid_rule.go source/custom: move rule expressions to pkg/apis/nfd/v1alpha1 2021-11-16 18:12:16 +02:00
kconfig_rule.go source/kernel: unmangled kconfig values for custom rules 2021-12-02 10:06:21 +02:00
loaded_kmod_rule.go source/custom: move rule expressions to pkg/apis/nfd/v1alpha1 2021-11-16 18:12:16 +02:00
nodename_rule.go source/custom: move rule expressions to pkg/apis/nfd/v1alpha1 2021-11-16 18:12:16 +02:00
pci_id_rule.go source/custom: move rule expressions to pkg/apis/nfd/v1alpha1 2021-11-16 18:12:16 +02:00
usb_id_rule.go source/custom: move rule expressions to pkg/apis/nfd/v1alpha1 2021-11-16 18:12:16 +02:00