Do not prefix label names from the new matchFeatures/matchAny custom rules with "custom-". We want to have the same result (set of labels) from a rule independent of whether it has been specified in worker config or in a NodeFeatureRule CRs. Legacy matchOn rules (not available in NodeFeatureRule CRs) are intact, i.e. still prefixed, in order to retain backwards compatibility.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.11.0 extras and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5070