Migrate away from google.com gcp project kubernetes-e2e-test-images

[spiffxp]

Related:

• Part of umbrella issue to migrate away from google.com gcp projects: Umbrella issue: migrate away from google.com gcp projects #1469
• Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: Registries used in k/k CI should be on Kubernetes Community infra #1458
• Companion issue to Use k8s.gcr.io/e2e-test-images instead of gcr.io/kubernetes-e2e-test-images for e2e test images kubernetes#96770

We should migrate away from the google.com-owned gcr.io/kubernetes-e2e-test-images and instead use the community-owned k8s.gcr.io/e2e-test-images repository.

Once we have done so, we should:

• announce a deprecation window: https://groups.google.com/g/kubernetes-dev/c/jIrBjnw3cDg
• flag project for deletion post-deprecation: post-deprecation-window: turn down kubernetes-e2e-test-images GCP project #3112

/wg k8s-infra
/sig testing
/sig release
/area release-eng

[spiffxp]

/assign @claudiubelu @aojea
who have done a fair amount of work on this already
/assign @spiffxp
/milestone v1.21

[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-contributor-experience at kubernetes/community.
/lifecycle stale

[ameukam]

/remove-lifecycle stale
/milestone clear

[spiffxp]

/milestone v1.22
I believe we are close on this

[spiffxp]

Current status:

• v1.23 now uses k8s.gcr.io/e2e-test-images: Use k8s.gcr.io/e2e-test-images instead of gcr.io/kubernetes-e2e-test-images for e2e test images kubernetes#96770
• we have not announced a deprecation window

[spiffxp]

There also remain a number of references to gcr.io/kubernetes-e2e-test-images through the project: https://cs.k8s.io/?q=gcr.io%2Fkubernetes-e2e-test-images&i=nope&files=&excludeFiles=vendor%2F&repos=

[spiffxp]

Repos that may need references updated in checklist form:

curl -s -X POST \
  -F "q=gcr.io/kubernetes-e2e-test-images" \
  -F "repos=*" \
  -F "excludeFiles=vendor/" \
  "https://cs.k8s.io/api/v1/search" \
| jq -r '.Results | keys | .[]' \
| sort \
| sed -e 's/^/- [ ] /g'

• kubernetes-sigs/cri-tools: Updates E2E test images registry kubernetes-sigs/cri-tools#831
• kubernetes-sigs/lwkd - n/a, historical reference
• kubernetes-sigs/metrics-server: Updates E2E test images registry kubernetes-sigs/metrics-server#847
• kubernetes-sigs/release-notes: n/a, historical reference
• kubernetes-sigs/windows-testing: images: use k8s.gcr.io/e2e-test-images kubernetes-sigs/windows-testing#290
• kubernetes/ingress-gce: Updates E2E test images registry ingress-gce#1577
• kubernetes/ingress-nginx: Updates E2E test images registry ingress-nginx#7704
• kubernetes/kubernetes: n/a, historical reference
• kubernetes/minikube: Updates E2E test images registry minikube#12584
• kubernetes/perf-tests: Updates E2E test images registry perf-tests#1899
• kubernetes/sig-release: n/a, historical reference
• kubernetes/test-infra: Replace usage of gcr.io/kubernetes-e2e-test-images test-infra#24223
• kubernetes/website: replace dnsutils example image website#30350

EDIT: updated as of 2021-11-03

[claudiubelu]

I can take a look at them.

[claudiubelu]

For lwkd, release-notes, and sig-release, it's noop. They only contain the release note regarding this migration:

./lwkd/_posts/2021-08-15-update.md:* [`k8s.gcr.io/e2e-test-images`](https://github.com/kubernetes/kubernetes/pull/103796) is the new `gcr.io/kubernetes-e2e-test-images`
./release-notes/src/assets/release-notes-1.23.0-alpha.1.json:    "markdown": "The image `gcr.io/kubernetes-e2e-test-images` will no longer be used in E2E / CI testing, `k8s.gcr.io/e2e-test-images` will be used instead. ([#103724](https://github.com/kubernetes/kubernetes/pull/103724), [@claudiubelu](https://github.com/claudiubelu))",
./release-notes/src/assets/release-notes-1.23.0-alpha.1.json:    "text": "The image `gcr.io/kubernetes-e2e-test-images` will no longer be used in E2E / CI testing, `k8s.gcr.io/e2e-test-images` will be used instead.",
./sig-release/releases/release-1.23/release-notes/maps/pr-103724-map.yaml:  text: The image `gcr.io/kubernetes-e2e-test-images` will no longer be used in E2E
./sig-release/releases/release-1.23/release-notes/release-notes-draft.json:    "markdown": "The image `gcr.io/kubernetes-e2e-test-images` will no longer be used in E2E / CI testing, `k8s.gcr.io/e2e-test-images` will be used instead. ([#103724](https://github.com/kubernetes/kubernetes/pull/103724), [@claudiubelu](https://github.com/claudiubelu))",
./sig-release/releases/release-1.23/release-notes/release-notes-draft.json:    "text": "The image `gcr.io/kubernetes-e2e-test-images` will no longer be used in E2E / CI testing, `k8s.gcr.io/e2e-test-images` will be used instead.",
./sig-release/releases/release-1.23/release-notes/release-notes-draft.md:- The image `gcr.io/kubernetes-e2e-test-images` will no longer be used in E2E / CI testing, `k8s.gcr.io/e2e-test-images` will be used instead. ([#103724](https://github.com/kubernetes/kubernetes/pull/103724), [@claudiubelu](https://github.com/claudiubelu))

[spiffxp]

kubernetes/website is the last remaining non-historical reference. There are some example and blog posts referencing the old repo. The problem is that the new repo doesn't have identical / equivalent images. I'm going to look at using gcrane or something to sync some more containers over to k8s-staging-e2e-test-images and promote accordingly.

[spiffxp]

Perhaps better to just update the examples...

[spiffxp]

Opened a followup issue to decommission the project post-deprecation: #3112

Will draft an announcement after test freeze

[spiffxp]

/close

Deprecation announced: https://groups.google.com/g/kubernetes-dev/c/jIrBjnw3cDg

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close

Deprecation announced: https://groups.google.com/g/kubernetes-dev/c/jIrBjnw3cDg

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.