Hi @pacoxu. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

/cc @dims

@pacoxu: GitHub didn't allow me to request PR reviews from the following users: dmis.

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

@pacoxu Let's land this here closer to the k8s 1.25 release and not before. is that fair? thanks!

@pacoxu Let's land this here closer to the k8s 1.25 release and not before. is that fair? thanks!

OK.

We meet a problem in kubeadm/kinder e2e test on the latest kubeadm on the old kubelet(n-1 version). The problem is for the loaded image is gcr image and kubeadm is using registry.k8s.io(kinder needs to load the image before using it.). We should take attention to similar issues in some e2e tests. Details in #7038.

@pacoxu ack, let's see if we can fix it on kinder side?

I found that kubernetes-sigs/kind#2688 is adding this repo as a mirror of the other.

• This will cause kind to pull from registry.k8s.io first before k8s.gcr.io directly if that fails.

@dims
kubernetes v1.25 is out.

/ok-to-test

Would it make sense to cherry-pick this to 1.5 and 1.6? Explicit new name of registry may be better than the redirect that may soon be introduced.