CoreDNS to use gcr.io repo

[rajansandeep]

What this PR does / why we need it:
Switch CoreDNS to use the gcr.io in kubeadm

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:

Release note:

CoreDNS deployment configuration now uses k8s.gcr.io imageRepository

[rajansandeep]

Opening this PR which makes the same changes as #59753. The original author of the PR @nashasha1 doesn't seem to be active and wanted to make sure that these changes get in before code freeze.
/cc @luxas
/cc @timothysc

[roberthbailey]

/milestone v1.11

[luxas]

/lgtm
/approve

Thanks!

[roberthbailey]

kind/cleanup

[roberthbailey]

priority/important-soon

[roberthbailey]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: luxas, rajansandeep, roberthbailey

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:

• cmd/kubeadm/OWNERS [luxas]

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

[roberthbailey]

/status approved-for-milestone

[rajansandeep]

@roberthbailey @luxas thank you for the quick response!!

[roberthbailey]

/test pull-kubernetes-integration

[tpepper]

FYI: This PR is not marked as priority/critical-urgent. As such, it will be removed from the 1.11 milestone by the milestone bot when Code Freeze starts at midnight UTC / 5pm PDT. If you feel it is critical to 1.11, please upgrade its priority to critical-urgent.

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process

@luxas @rajansandeep @roberthbailey

Pull Request Labels

• sig/cluster-lifecycle: Pull Request will be escalated to these SIGs if needed.
• priority/critical-urgent: Never automatically move pull request out of a release milestone; continually escalate to contributor and SIG through all available channels.
• kind/cleanup: Adding tests, refactoring, fixing old bugs.

Help

• Additional instructions
• Commands for setting labels

[roberthbailey]

@tpepper - I've been watching this PR today; it's currently in the batch submit being tested. If it doesn't merge before the code freeze I'll update the labels, since we do want it to make the release cut.

--edit--

It looks like @timothysc already updated the labels.

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 63322, 64718, 64708, 64775, 64777). If you want to cherry-pick this change to another branch, please follow the instructions here.