📖 use k8s-staging-ci-images vs kubernetes-ci-images

[spiffxp]

What this PR does / why we need it:

Document that the default CI images are pulled from
gcr.io/k8s-staging-ci-images, not gcr.io/kubernetes-ci-images

This was changed via kubernetes/kubernetes#97087
which landed 2021-01-14

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

Related:

• This is part of Deprecate and migrate away from gs://kubernetes-release-dev and gcr.io/kubernetes-ci-images kubernetes/k8s.io#2318
• More specifically Migrate away from google.com gcp project kubernetes-ci-images kubernetes/k8s.io#1460

[spiffxp]

/cc @detiber @vincepri

[neolit123]

i think this repository is stale and the code now lives under a k-sigs/cluster-api folder.
@vincepri @fabriziopandini is time to archive this repository?

[vincepri]

Yes it can be archived.

[neolit123]

@vincepri
i will log an issue in k-sigs/cluster api as there are number of action items here, including test-infra cleanup.
EDIT: kubernetes-sigs/cluster-api#5037

@spiffxp i think we can merge this to omit it from the org search (e.g. https://cs.k8s.io/).
/lgtm
/approve

[neolit123]

i cannot merge it because i'm not in owners.
/assign @vincepri

[vincepri]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neolit123, spiffxp, vincepri

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:

• OWNERS [vincepri]

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