Migrate away from google.com gcp project k8s-testimages

[spiffxp]

Part of umbrella issue to migrate away from google.com gcp projects: #1469

Umbrella issue for migrating or removing dependence on all of the kubernetes project infra that lives under k8s-testimages

Full list of images:

$ gcloud container images list --repository gcr.io/k8s-testimages
NAME
gcr.io/k8s-testimages/alpine-bash
gcr.io/k8s-testimages/aws-janitor
gcr.io/k8s-testimages/bazel-krte
gcr.io/k8s-testimages/bazelbuild
gcr.io/k8s-testimages/benchmarkjunit
gcr.io/k8s-testimages/bigquery
gcr.io/k8s-testimages/bootstrap
gcr.io/k8s-testimages/bootstrap-dind
gcr.io/k8s-testimages/boskos
gcr.io/k8s-testimages/boskosctl-base
gcr.io/k8s-testimages/branchprotector
gcr.io/k8s-testimages/cherrypick
gcr.io/k8s-testimages/cluster-api
gcr.io/k8s-testimages/commenter
gcr.io/k8s-testimages/dind-test-base-amd64
gcr.io/k8s-testimages/e2e-kubeadm
gcr.io/k8s-testimages/e2e-kubemci
gcr.io/k8s-testimages/experiment
gcr.io/k8s-testimages/fake-server
gcr.io/k8s-testimages/fedtidy
gcr.io/k8s-testimages/gcb-docker-gcloud
gcr.io/k8s-testimages/gcloud-bazel
gcr.io/k8s-testimages/gcloud-in-go
gcr.io/k8s-testimages/gcp-controller-manager
gcr.io/k8s-testimages/gcr.io
gcr.io/k8s-testimages/gencred
gcr.io/k8s-testimages/ghproxy
gcr.io/k8s-testimages/github-fetcher
gcr.io/k8s-testimages/github-token-counter
gcr.io/k8s-testimages/github-transform
gcr.io/k8s-testimages/gob-test
gcr.io/k8s-testimages/grafana
gcr.io/k8s-testimages/greenhouse
gcr.io/k8s-testimages/gubernator
gcr.io/k8s-testimages/heapster-test
gcr.io/k8s-testimages/image-builder
gcr.io/k8s-testimages/issue-creator
gcr.io/k8s-testimages/janitor
gcr.io/k8s-testimages/janitor-aws
gcr.io/k8s-testimages/kettle
gcr.io/k8s-testimages/krte
gcr.io/k8s-testimages/kube-deploy
gcr.io/k8s-testimages/kubekins-e2e
gcr.io/k8s-testimages/kubekins-e2e-prow
gcr.io/k8s-testimages/kubekins-node
gcr.io/k8s-testimages/kubekins-senlu-hack
gcr.io/k8s-testimages/kubekins-test
gcr.io/k8s-testimages/kubemark
gcr.io/k8s-testimages/kubernetes-node
gcr.io/k8s-testimages/label_sync
gcr.io/k8s-testimages/launcher.gcr.io
gcr.io/k8s-testimages/levee-test
gcr.io/k8s-testimages/logexporter
gcr.io/k8s-testimages/metrics
gcr.io/k8s-testimages/misc-mungers
gcr.io/k8s-testimages/nursery
gcr.io/k8s-testimages/perf-tests-util
gcr.io/k8s-testimages/perfdash
gcr.io/k8s-testimages/planter
gcr.io/k8s-testimages/probes
gcr.io/k8s-testimages/prow-test-image
gcr.io/k8s-testimages/quay.io
gcr.io/k8s-testimages/queue-health-base
gcr.io/k8s-testimages/queue-health-graph
gcr.io/k8s-testimages/queue-health-poll
gcr.io/k8s-testimages/reaper
gcr.io/k8s-testimages/redis
gcr.io/k8s-testimages/resultstore
gcr.io/k8s-testimages/submit-queue
gcr.io/k8s-testimages/test-infra-go-test
gcr.io/k8s-testimages/test-infra-py-test
gcr.io/k8s-testimages/triage

I suspect not all of these images need to be migrated over. We may also need to watch out for some of these images being consumed by other projects (accept the cost? leave them where they are? rename and force a break?)

I would suggest breaking up into:

• images used by kubernetes/kubernetes e2e jobs (e.g. kubekins)
• images used by other kubernetes CI jobs (e.g. gcloud-in-go)
• images used by other test-infra components that don't already have k8s.gcr.io equivalents (e.g. kettle)

[ameukam]

/area artifacts

[spiffxp]

/close
Closing in favor of #1523

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
Closing in favor of #1523

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.