Find China mirror URLs for Kubernetes components to fix slow access to official registries.
https://registry.aliyuncs.com/google_containerskubeadm pull command
kubeadm config images pull --image-repository https://registry.aliyuncs.com/google_containershttps://k8s.m.daocloud.iokubeadm pull command
kubeadm config images pull --image-repository https://k8s.m.daocloud.iohttps://repo.huaweicloud.com/kuberneteskubeadm pull command
kubeadm config images pull --image-repository https://repo.huaweicloud.com/kuberneteshttps://mirror.ccs.tencentyun.com/k8skubeadm pull command
kubeadm config images pull --image-repository https://mirror.ccs.tencentyun.com/k8shttps://k8sgcr.azk8s.cn/google-containerskubeadm pull command
kubeadm config images pull --image-repository https://k8sgcr.azk8s.cn/google-containershttps://gcr.mirrors.ustc.edu.cn/google-containerskubeadm pull command
kubeadm config images pull --image-repository https://gcr.mirrors.ustc.edu.cn/google-containersWhen users in China pull Kubernetes component images from official registries like registry.k8s.io, downloads often time out or fail due to network restrictions. This tool aggregates domestic image registries such as Alibaba Cloud and Tencent Cloud, converting official image names into accessible China mirror URLs. This reduces the pull time for core components like kube-apiserver from hours to mere minutes.
registry.k8s.io/kube-apiserver:v1.28.0.--image-repository parameter to your kubeadm init command to replace the default registry.How do I verify if an image is synced?
Run docker pull [image_url] to test the pull speed. It should normally complete within 2 minutes.
Which K8S components are supported?
Currently covers core components like kube-apiserver and base images like pause. Third-party images such as CNI plugins are not included at this time.
Some images may experience a sync delay of up to 24 hours. We recommend verifying them in advance for production environments. Do not host sensitive component images on untrusted third-party registries.
For kubeadm deployments, it is recommended to configure a global image accelerator in /etc/containerd/config.toml. Typical configuration example:[plugins."io.containerd.grpc.v1.cri".registry.mirrors]
["registry.k8s.io"]
endpoint = ["https://registry.aliyuncs.com/google_containers"]
