Wildcard for matching against all keys in label rules

[marquiz]

Extend the feature rule format with a special wildcard that can be used
in matchExpressions. By using '*' as the field name in an expressoin
makes is possible to run the expression agains all feature names,
instead of the value of one feature.

This can be useful in template rules for creating per-feature labels,
based on feature names (instead of values) and in "normal"
(non-template) rules for checking if (at least) one of certain feature
names are present.

An example of creating an "avx512" label if any AVX512* CPUID feature is
present:

  - name: "avx512-any-feature"
    labels: {avx512: "true"}
    matchFeatures:
      - feature: cpu.cpuid:
        matchExpressions:
          "*": {op: InRegexp, value: ["^AVX512"]}

An example of a template rule creating a dynamic set of labels based on
the existence of kconfig options.

  - name: "kconfig-template-features"
    labelsTemplate: |
      {{range .kernel.config}}kconfig-{{.Name}}={{.Value}}
      {{end}}
    matchFeatures:
      - feature: kernel.config
        matchExpressions:
          "*": {op: In, value: [SWAP, X86, ARM]}

Depends on #550

[marquiz]

/hold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marquiz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [marquiz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla

[k8s-ci-robot]

@marquiz: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[marquiz]

I don't like this approach myself. Possibly something like this would be more comprehensive:

  - name: "avx512-any-feature"
    labels: {avx512: "true"}
    matchFeatures:
      - feature: cpu.cpuid:
        matchNames: {op: InRegexp, value: ["^AVX512"]}

[k8s-ci-robot]

@marquiz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-node-feature-discovery-build-image-cross	7f253e4	link	true	/test pull-node-feature-discovery-build-image-cross

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[marquiz]

Moving milestone to v0.12.0

[marquiz]

Supserseded by #788
/close

[k8s-ci-robot]

@marquiz: Closed this PR.

In response to this:

Supserseded by #788
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.