post-deprecation-window: turn down kubernetes-ci-images GCP project

[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
• Followup to: Migrate away from google.com gcp project kubernetes-ci-images #1460

We've stopped writing new data to this project.

This project can be turned down either:

• 1 year after the release of v1.22 (which should ideally be after the release of v1.25 based on the project's new 3 releases/year cadence), ref: https://kubernetes.io/releases/version-skew-policy/#supported-versions
• when there is negligible traffic to gcr.io/kubernetes-ci-images

/wg k8s-infra

/sig release
/area artifacts
/area release-eng
FYI @kubernetes/release-engineering

/kind cleanup
/kind deprecation
/priority backlog
/milestone v1.25

[spiffxp]

/triage accepted
/lifecycle frozen
This is going to need to stay open for a while, but I've bumped its priority down and put in a milestone to signify it's a thing we care about

[ameukam]

/milestone v1.26

[Riaankl]

@ameukam should this be added to /milestone v1.27 ?

[ameukam]

No. Let's extend the deprecation period.

/milestone clear

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted