We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Browse mirror reference addresses, with a documented DaoCloud mapping for registry.k8s.io.
Reference addresses, not a live availability test. DaoCloud documents its registry mapping; the other addresses are historical, unverified entries. Check the required image tag, architecture and digest before use.
https://registry.aliyuncs.com/google_containersHistorical address; current availability and coverage are unverified.
https://k8s.m.daocloud.ioMaintainer-documented mapping (reviewed 2026-09-29); availability and tag coverage vary.
kubeadm pull command
kubeadm config images pull --image-repository k8s.m.daocloud.iohttps://repo.huaweicloud.com/kubernetesHistorical address; current availability and coverage are unverified.
https://mirror.ccs.tencentyun.com/k8sHistorical address; current availability and coverage are unverified.
https://k8sgcr.azk8s.cn/google-containersHistorical address; current availability and coverage are unverified.
https://gcr.mirrors.ustc.edu.cn/google-containersHistorical address; current availability and coverage are unverified.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page is a small address reference for people preparing Kubernetes images, especially when working with a network in China. Filter the list by a mirror name or part of its address, then copy the registry address shown in a result. It does not accept a full image name or tag, query a registry, or report whether an image is currently available.
The six entries are Alibaba Cloud (registry.aliyuncs.com/google_containers), DaoCloud (k8s.m.daocloud.io), Huawei Cloud (repo.huaweicloud.com/kubernetes), Tencent Cloud (mirror.ccs.tencentyun.com/k8s), Azure China (k8sgcr.azk8s.cn/google-containers), and USTC (gcr.mirrors.ustc.edu.cn/google-containers). DaoCloud is the only entry currently accompanied by a maintainer-documented mapping for registry.k8s.io and a kubeadm example. The other five are historical reference entries whose current availability and image coverage have not been verified.
A registry reference is the host and optional path prefix before an image name and tag. For example, registry.k8s.io/kube-apiserver:v1.XX.Y identifies an image name and tag under a registry. Replacing the registry prefix can change the full path expected by the destination. A copied address is therefore a starting point for configuration, not proof that the same image, tag, architecture, or digest exists there.
DaoCloud's maintainer repository maps registry.k8s.io to k8s.m.daocloud.io and shows that value as kubeadm's imageRepository. Kubernetes documents --image-repository for selecting the registry used by kubeadm and cautions that paths under a custom repository can differ from the defaults. Read the DaoCloud mapping and the Kubernetes kubeadm configuration reference before applying a change.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter a provider name such as DaoCloud, or paste a distinctive URL fragment into the keyword filter. Clear the field to see the full reference list again.
Read the status beside the result. The DaoCloud mapping is documented by its maintainer; the other five entries are marked historical and unverified. Copy the address only if its status and intended use fit your review process.
For kubeadm, compare the copied registry value with your planned Kubernetes version and the image paths produced by kubeadm config images list. The reference includes a copyable pull-command form for DaoCloud: kubeadm config images pull --image-repository k8s.m.daocloud.io. Add the version or configuration options needed for your cluster.
Test in the same network, runtime, and target architecture as the cluster. Check the resulting image reference and digest against the source you intend to trust before using it in installation configuration.
Use your target cluster's kubeadm version and configuration to list the exact images first. Kubernetes notes that custom repositories can use paths that differ from the default path layout. Review the output rather than assuming a prefix substitution preserves every path. For details, see the official kubeadm image guidance.
Use cases
See how the tool fits into real work and everyday tasks.
An administrator can filter for DaoCloud, copy its documented registry reference, and compare the target version's generated image list before attempting a pull from the node's own network.
A team maintaining a runbook can use the address list as a prompt to check a proposed repository value. The runbook should record the Kubernetes version, full image paths, and verification results instead of treating a listed address as proof of coverage.
Q&A
Find concise answers to common questions and confusing cases.
No. It filters a fixed reference list. It does not contact the listed registries or measure reachability, speed, synchronization, or image availability.
Only the DaoCloud result has a kubeadm command and a current maintainer-documented mapping in the checked sources. Treat the other five as historical, unverified entries. Even a documented repository must be checked against the image paths required by your kubeadm version.
No. A registry prefix does not confirm a particular image, tag, architecture, or digest. Generate the image list for the target Kubernetes version, then verify the exact references in the intended runtime environment.
Notes
Review scope, result limitations, and important precautions before use.
Mirror endpoints and their policies can change. This reference does not test current availability, tag coverage, architecture support, freshness, image integrity, or provider retention. DaoCloud's documented mapping is evidence of the stated configuration, not a guarantee that each requested artifact will be served at the time you pull it. Confirm current maintainer guidance, network access, certificate behavior, full paths, and image digests before using a mirror in a production environment. For higher assurance, follow Kubernetes guidance to prepare images in a registry you control and trust.
The kubeadm command shown is a pull example with a registry setting. It does not select a Kubernetes version or rewrite application images in workload manifests. Keep the configured version, image list, registry path, and cluster configuration consistent.
Related
Discover related tools, collections, and available API capabilities.