tests: Removed hardcoded images from yaml files

[claudiubelu]

What this PR does / why we need it:

Some tests use .yaml files to deploy pods, which have hardcoded
images. Those images cannot be used for Windows containers.

The image names can be injected by the tests themselves, based on
the configured registries.

Related to issue #60487

Special notes for your reviewer:

Release note:

NONE

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

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.

[wgliang]

/ok-to-test

[claudiubelu]

/retest

[claudiubelu]

/assign @kow3ns

[PatrickLang]

/lgtm - fixes some Windows tests

[PatrickLang]

/test pull-kubernetes-bazel-build

[spiffxp]

So I'm not sure about turning those doc .yaml files into templates, please see if docs are using them... but if they're ok to template, then I'd prefer if we could use something less brittle if new templates/images are added

[PatrickLang]

@BCLAU - can you update based on the feedback above?

[AishSundar]

@PatrickLang you will need /priority and /kind labels for this PR to be able to merge

[dims]

per discussion in sig-arch, let's move this out to 1.14

/milestone v1.14

[spiffxp]

two nits, nearly there

[claudiubelu]

/test pull-kubernetes-godeps

[dims]

/assign @spiffxp @ixdy

@kubernetes/sig-testing-pr-reviews can you please take a look?

[k8s-ci-robot]

@BCLAU: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-kubemark-e2e-gce	95f125bd35b9e19fc3f5007b97b8d86054a7a7b0	link	/test pull-kubernetes-kubemark-e2e-gce

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.

[claudiubelu]

/test pull-kubernetes-kubemark-e2e-gce
/test pull-kubernetes-kubemark-e2e-gce-big

[ixdy]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bclau, ixdy

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 [ixdy]

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