cluster-up, kind, common: Enable TopologyManager for kind-sriov

[nirdothan]

SRIOV tests check topology alignemnt. Currently in kind/sriov kueblet does not attempt to align resources hence topology tests don't really validate anything of interest. Add topology manager[1] to kubelet config and set its policy to single-numa-node. Together with cpu-manager policy =static, which we already set, kubelet will reject a pod that it is unable to align. It has been tested sucesfully in a kubevirt/kubevirt PR[2] [1] https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/ [2] kubevirt/kubevirt#13685

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

NONE

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dhiller 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:

• OWNERS

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

[nirdothan]

/retest-required

[nirdothan]

/retest-required

[nirdothan]

Changed topology manager policy to restricted as sriov tests failed since scheduler could not allocate all resources on a single numa (I suspect)

[nirdothan]

/retest-required

[brianmcarey]

/test check-up-kind-sriov

[nirdothan]

/test check-up-kind-sriov

@brianmcarey @ormergi It's probably failing barbecue of #1348

[ormergi]

/test check-up-kind-sriov

@brianmcarey @ormergi It's probably failing barbecue of #1348

I dont see why #1348 cuasing this PR is failing.
Looking into the last failure logs, it seems kubevirt deployment failed
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirtci/1347/check-up-kind-sriov/1879983806077734912#1:build-log.txt%3A2473

If anything, I hope we can get #1348 merged as soon as possible in favor of returning the lane to be required.

[kubevirt-bot]

@nirdothan: 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
check-provision-k8s-1.31-s390x	20855e2	link	true	/test check-provision-k8s-1.31-s390x
check-up-kind-sriov	20855e2	link	false	/test check-up-kind-sriov

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-sigs/prow repository. I understand the commands that are listed here.