Marc Sluiter 7038e49d02 source/custom: Add nodename rule ... There are cases when the only available metadata for discovering features is the node's name. The "nodename" rule extends the custom source and matches when the node's name matches one of the given nodename regexp patterns. It is also possible now to set an optional "value" on custom rules, which overrides the default "true" label value in case the rule matches. In order to allow more dynamic configurations without having to modify the complete worker configuration, custom rules are additionally read from a "custom.d" directory now. Typically that directory will be filled by mounting one or more ConfigMaps. Signed-off-by: Marc Sluiter <msluiter@redhat.com>		2021-02-24 16:26:35 +01:00
..
cpuid_rule.go	source/custom: add rules for cpuid and kconfig	2020-09-14 12:07:35 +03:00
kconfig_rule.go	source/custom: add rules for cpuid and kconfig	2020-09-14 12:07:35 +03:00
loaded_kmod_rule.go	Implement the 'custom' feature Source	2020-03-19 09:31:59 +02:00
nodename_rule.go	source/custom: Add nodename rule	2021-02-24 16:26:35 +01:00
pci_id_rule.go	source/custom: make linter happy	2020-05-20 21:48:06 +03:00
rule.go	Add Match Rules package to be used in Custom Source	2020-03-17 18:00:05 +02:00
usb_id_rule.go	source/custom: make linter happy	2020-05-20 21:48:06 +03:00