Fix CreateSecPodWithNodeName to properly set node to be deployed

[mkimuram]

What type of PR is this?
/kind failing-test

What this PR does / why we need it:
Fix CreateSecPodWithNodeName to properly set node to be deployed.
This bug cause [Testpattern: Dynamic PV (filesystem volmode)] volumeMode[Feature:BlockVolume] should create sc, pod, pv, and pvc, read/write to the pv, and delete all created resources test for csi-hostpath driver fail.

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

This only address csi hostpath test for 70760.

Special notes for your reviewer:
/sig storage

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @mkimuram. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[mkimuram]

Manifest for the pod inside the daemonset for csi-hostpath plugin is changed by patching with PatchCSIOptions, as a result, csi-hostpath pod only deployed in h.driverInfo.Config.ServerNodeName. So, test pod should be deployed on the same node.
On the other hand, CreateSecPodWithNodeName failed to set the node where the pod should be deployed. As a result, this test for csi-hostpath fails.

[msau42]

/ok-to-test
/lgtm
/approve

[mkimuram]

/retest

[AishSundar]

/priority important-soon
/milestone v1.13

[mkimuram]

/retest

[mkimuram]

@msau42 @gnufied @davidz627 @AishSundar @jberkus

This will partially fix #70760 .
Now all tests have passed. And it seems that there needs one more approval to merge this.

Could you approve or assign someone approve this?

[msau42]

/assign @saad-ali

[davidz627]

/lgtm
beat me to it 🥇

[saad-ali]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkimuram, msau42, saad-ali

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/OWNERS [saad-ali]

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

[davidz627]

/test pull-kubernetes-integration

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel comment for consistent failures.