Gateway-api branch v1.3.0 has an ambiguous shortname image in coreDNS deployment

[rhamini3]

What happened:
The gateway-api conformance test is failing because the coredns-xx-xxxx pod has an ImagePullBackOff error because cri-o enforces unambiguous image names PR

What you expected to happen:
Expect the current image name to be accepted and the pod to show ready status

How to reproduce it (as minimally and precisely as possible):
Attempt to run the upstream conformance tests from the release-1.3 branch

Anything else we need to know?:
Creating this as a place holder, a linked fix is provided

[youngnick]

Thanks for this @rhamini3, can you check if this applies to v1.4, which was released recently? If so, we can roll a fix into a v1.4.1, which will probably come soon anyway.

[rhamini3]

Hi @youngnick this issue was fixed in release-1.4 branch it was overlooked in v1.3