WIP: kubelet: add a way to toggle the devicemanager check

[ffromani]

WIP TBD

[openshift-ci-robot]

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 369e7df|WIP: kubelet: add a way to toggle the devicemanager check: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ffromani
Once this PR has been reviewed and has the lgtm label, please assign sjenning for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• pkg/kubelet/DOWNSTREAM_OWNERS

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

[openshift-ci-robot]

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• aa7d7f4|WIP: kubelet: add a way to toggle the devicemanager check: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[swatisehgal]

/cc

[ffromani]

/cc @fabiand @stu-gott @xpivarc @MarSik @yanirq

this is still very much WIP but the basic concept is in place.
Should the default be old-behavior ("relaxed") or new-behavior ("strict")?

[openshift-ci]

@ffromani: GitHub didn't allow me to request PR reviews from the following users: xpivarc.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @fabiand @stu-gott @xpivarc @MarSik @yanirq

this is still very much WIP but the basic concept is in place.
Should the default be old-behavior ("relaxed") or new-behavior ("strict")?

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.

[ffromani]

converting to draft to save CPU cycles

[openshift-ci]

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

Test name	Commit	Details	Required	Rerun command
ci/prow/verify-commits	aa7d7f4	link	true	/test verify-commits
ci/prow/e2e-agnostic-ovn-cmd	aa7d7f4	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp	aa7d7f4	link	true	/test e2e-gcp
ci/prow/e2e-gcp-ovn-upgrade	aa7d7f4	link	true	/test e2e-gcp-ovn-upgrade

Full PR test history. Your PR dashboard.

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.

[ffromani]

obsoleted by #1618

[ffromani]

no longer needed, we validated/we are validating the PR in a different way