chore(scheduler): add filter integration tests for missing part plugins: NodeResources plugin

[googs1025]

What type of PR is this?

/kind cleanup
/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes part of #129856

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

None

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

@haosdent: The label(s) sig/scheduler cannot be applied, because the repository doesn't have them.

In response to this:

/sig scheduler

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.

[haosdent]

/sig scheduling

[googs1025]

/cc @macsko @sanposhiho

[macsko]

Maybe make the incomingPod schedulable if the existingPod would not exist, e.g.
node: 3 CPU
existingPod: 2 CPU
incomingPod: 2 CPU

[googs1025]

done

[macsko]

I meant to change the pod does not fit due to insufficient node resources test to:

			node: st.MakeNode().Name("insufficient-node").Capacity(
				map[v1.ResourceName]string{
					v1.ResourceCPU:    "3",
					v1.ResourceMemory: "3G",
				}).Obj(),
			existingPod: st.MakePod().Name("insufficient-existing-pod").
				Res(map[v1.ResourceName]string{
					v1.ResourceCPU:    "2",
					v1.ResourceMemory: "2G",
				}).Container(pause).
				Obj(),
			incomingPod: st.MakePod().Name("insufficient-incoming-pod").
				Res(map[v1.ResourceName]string{
					v1.ResourceCPU:    "2",
					v1.ResourceMemory: "2G",
				}).Container(pause).
				Obj(),
			fit: false,

Then we will see if the existingPod is really taken into account by the plugin.

[googs1025]

oh, I missunstand, done

[macsko]

Make it a single node, not slice?

[macsko]

The same with existingPods

[googs1025]

done

[macsko]

/remove-kind feature

[macsko]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b9f348b01e0d681db87a75f2bc20c17bfb161fc6

[googs1025]

/test pull-kubernetes-e2e-kind

[sanposhiho]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: googs1025, sanposhiho

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:

• test/integration/scheduler/OWNERS [sanposhiho]

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