Freeze k8s.gcr.io image registry

[upodroid]

Enhancement Description

• One-line enhancement description (can be used as a release note): Freeze k8s.gcr.io image registry
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/3720-freezing-k8s-gcr-io
• Discussion Link:
• Primary contact (assignee): @upodroid
• Responsible SIGs:
  • sig-k8s-infra
  • sig-release
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): N/A
  • Beta release target (x.y): N/A
  • Stable release target (x.y): 1.27
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3720: Freeze k8s.gcr.io image registry #3723
  • Code (k/k) update PR(s): Not relevant. Most changes will be in k/k8s.io, k/test-infra, k-sigs/promo-tools
  • Docs (k/website) update(s): Freeze k8s.gcr.io image registry website#39214

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/assign
/sig k8s-infra
/sig release
/stage stable

[puerco]

/cc

[sftim]

If we do this, I'd love to see a post on https://blog.k8s.io/ to announce the change.

[dims]

/milestone v1.27

[ameukam]

/label lead-opted-in

[npolshakova]

Hello @upodroid 👋, 1.27 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage stable for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[npolshakova]

Hi @upodroid,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

[BenTheElder]

Hi @npolshakova No PRs should be required to kubernetes/kubernetes. This is a project infrastructure change only, as kubernetes/kubernetes already migrated to only reference registry.k8s.io in prior releases.

This is still making progress.

[BenTheElder]

The next action is targeted for April 3rd: Actually ceasing to promote images to k8s.gcr.io. Related PRs will be primarily in https://github.com/kubernetes/k8s.io

We've communicated this to users in https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/

Though confusingly we're also working on phasing in a redirect from k8s.gcr.io to registry.k8s.io now this week.
That redirect cannot be depended on by users however and if anything happens to the redirect / during partial rollout we will not have new images at k8s.gcr.io after April 3rd.

[salehsedghpour]

/remove-label lead-opted-in

[BenTheElder]

@salehsedghpour is it necessary to do this for closed issues? This was opted in for tracking in 1.27, is marked 1.27+closed. I would assume closed issues are no longer tracked and/or we filter by milestone?

This seems like noise.

[salehsedghpour]

@BenTheElder You're right, it seems like a noise. According to Enhancements handbook, the Enhancements Lead should search for all lead-opted-in label and remove them all.

To make sure that this issue won't be shown to in such search, I removed it.

[BenTheElder]

ACK.

I think that should specify issues in the current milestone or open issues (an open discussion for release team which makes more sense), but somewhere between closed issues and closed milestones I would think we'd be done updating these issues ...