From 759e2c9cf5ba98cef4100328373b038160e17266 Mon Sep 17 00:00:00 2001 From: Mengjiao Liu Date: Tue, 8 Nov 2022 11:43:36 +0800 Subject: [PATCH] Use the `registry.k8s.io` instead of `k8s.gcr.io` image registry --- .../reference/setup-tools/kubeadm/implementation-details.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md b/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md index ced5a64e6a..a09b6d3b78 100644 --- a/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md +++ b/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md @@ -252,7 +252,7 @@ Static Pod manifest share a set of common properties: Please note that: -1. All images will be pulled from k8s.gcr.io by default. +1. All images will be pulled from registry.k8s.io by default. See [using custom images](/docs/reference/setup-tools/kubeadm/kubeadm-init/#custom-images) for customizing the image repository 1. In case of kubeadm is executed in the `--dry-run` mode, static Pods files are written in a