Move published artifacts images to use k8s.gcr.io

[vincepri]

As reported in Slack (https://kubernetes.slack.com/archives/C8TSNPY4T/p1595441096272200) by @detiber, after the new domain comes into effect, we should be able to safely switch our images to use k8s.gcr.io in all our artifacts.

We'll probably going to hold this change until we have some confirmation that the migration went smoothly, probably until early next week.

/kind cleanup
/milestone v0.3.8
/priority important-soon

[vincepri]

/milestone v0.3.x

[vincepri]

/milestone v0.4.0

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fabriziopandini]

/remove-lifecycle stale

[vincepri]

/priority backlog

[fabriziopandini]

@vincepri @detiber I'm trying to derive action items for this issue.

AFAIK, in CAPI we are publishing our with google cloud build and images are already replicated to {us, eu, asia}.gcr.io/k8s-artifacts-prod/cluster-api.

If this is true, should we now change our templates to fetch from k8s.gcr.io instead of us.gcr.io/k8s-artifacts-prod/cluster-api? is this the only change required in CAPI?

[vincepri]

Yes, we should switch the manifests at some point before releasing v1alpha4