You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each host should have access read and fetch images from the Kubernetes container image registry, `k8s.gcr.io`.
171
+
Each host should have access read and fetch images from the Kubernetes container image registry, `registry.k8s.io`.
172
172
If you want to deploy a highly-available cluster where the hosts do not have access to pull images, this is possible. You must ensure by some other means that the correct container images are already available on the relevant hosts.
@@ -392,7 +392,9 @@ option. Your cluster requirements may need a different configuration.
392
392
393
393
<!--
394
394
1. Apply the CNI plugin of your choice:
395
-
[Follow these instructions](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network) to install the CNI provider. Make sure the configuration corresponds to the Pod CIDR specified in the kubeadm configuration file (if applicable).
395
+
[Follow these instructions](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network)
396
+
to install the CNI provider. Make sure the configuration corresponds to the Pod CIDR specified in the
0 commit comments