Freeze the old k8s.gcr.io image registry

[upodroid]

Fixes: kubernetes/release#2947
Fixes: kubernetes/enhancements#3720

Merging this PR will freeze the old registry.

/cc @kubernetes/release-engineering @dims @BenTheElder

[k8s-ci-robot]

@upodroid: GitHub didn't allow me to request PR reviews from the following users: kubernetes/release-engineering.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Fixes: kubernetes/release#2947
Fixes: kubernetes/enhancements#3720

Merging this PR will freeze the old registry.

1st commit will delete the old registries

2nd commit will add the new AR registries we created. @ameukam What are the new rules?

/cc @kubernetes/release-engineering @dims @BenTheElder

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.

[ameukam]

2nd commit will add the new AR registries we created. @ameukam What are the new rules?

Not sure to understand the question but let's add the new AR regions in a different PR and probably after the redirect is done. the regional-equivalent buckets for those new AR repositories are still not created.

I also suggest we merge this PR on April 3th morning CET.

[upodroid]

sounds good

/hold till the 3rd of April

Not sure to understand the question but let's add the new AR regions in a different PR and probably after the redirect is done. the regional-equivalent buckets for those new AR repositories are still not created.

Correct. I meant regions instead of rules

[ameukam]

Correct. I meant regions instead of rules

See:

• Add more S3 regions registry.k8s.io#172 (comment)

[BenTheElder]

/hold

we're in progress to fully redirecting some images including tag lists currently so actually enacting the freeze is going to put us in a lose lose if we find any issues. Will start a slack thread for higher bandwidth in a moment. This is due to the skew issue with backing stores.

[upodroid]

@puerco Did we manage to fix the missing sigstore layers in the backing registries?

[puerco]

@upodroid We merged some improvements to the image promoter which should allow it to run with the AR rate limit, this should stop the problem from getting bigger.

The missing sigantures are still missing. We haven't run the remediation jobs yet as we agreed to wait until the redirect rollout is done, or at least getting it green lighted when there is enough confidence enough that the redirect is still within its error budget.

[TerryHowe]

Ready on this yet?

[BenTheElder]

Yes, yesterday we lifted kubernetes/registry.k8s.io#181, however the ROI is still lower than pre-redirect and many folks are away at KubeCon so it might not be the best week for this. I do still think we should do this.

[sftim]

We're now post-KubeCon.

[BenTheElder]

/hold cancel
/assign @thockin @dims

[thockin]

/approve

[thockin]

/lgtm

[upodroid]

I rebased the PR and picked up the latest set of registries. This is ready now

[BenTheElder]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, thockin, upodroid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thockin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment