post-deprecation-window: turn down kubernetes-e2e-test-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-e2e-test-images #1522

As of Kubernetes v1.23 we no longer use this project for e2e test images, and instead fully use k8s.gcr.io/e2e-test-images.

This project can be turned down either:

• 1 year after the release of v1.23 (which should ideally be after the release of v1.26 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-e2e-test-images

/wg k8s-infra

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

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

[k8s-ci-robot]

@spiffxp: The provided milestone is not valid for this repository. Milestones in this repository: [v1.23, v1.24, v1.25]

Use /milestone clear to clear the milestone.

In response to this:

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-e2e-test-images #1522

As of Kubernetes v1.23 we no longer use this project for e2e test images, and instead fully use k8s.gcr.io/e2e-test-images.

This project can be turned down either:

• 1 year after the release of v1.23 (which should ideally be after the release of v1.26 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-e2e-test-images

/wg k8s-infra

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

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

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.

[k8s-ci-robot]

@spiffxp: The label(s) wg/k8s-infra cannot be applied, because the repository doesn't have them.

In response to this:

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-e2e-test-images #1522

As of Kubernetes v1.23 we no longer use this project for e2e test images, and instead fully use k8s.gcr.io/e2e-test-images.

This project can be turned down either:

• 1 year after the release of v1.23 (which should ideally be after the release of v1.26 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-e2e-test-images

/wg k8s-infra

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

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

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.

[spiffxp]

/sig k8s-infra

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ameukam]

/remove-lifecycle stale