@@ -494,31 +494,35 @@ This process (steps 3-6) can also be triggered with `kubeadm phase selfhosting c
494494
495495For running kubeadm without an internet connection you have to pre-pull the required master images for the version of choice :
496496
497- | Image Name | v1.8 release branch version | v1.9 release branch version |
498- |----------------------------------------------------------|-----------------------------|-----------------------------|
499- | k8s.gcr.io/kube-apiserver-${ARCH} | v1.8.x | v1.9.x |
500- | k8s.gcr.io/kube-controller-manager-${ARCH} | v1.8.x | v1.9.x |
501- | k8s.gcr.io/kube-scheduler-${ARCH} | v1.8.x | v1.9.x |
502- | k8s.gcr.io/kube-proxy-${ARCH} | v1.8.x | v1.9.x |
503- | k8s.gcr.io/etcd-${ARCH} | 3.0.17 | 3.1.10 |
504- | k8s.gcr.io/pause-${ARCH} | 3.0 | 3.0 |
505- | k8s.gcr.io/k8s-dns-sidecar-${ARCH} | 1.14.5 | 1.14.7 |
506- | k8s.gcr.io/k8s-dns-kube-dns-${ARCH} | 1.14.5 | 1.14.7 |
507- | k8s.gcr.io/k8s-dns-dnsmasq-nanny-${ARCH} | 1.14.5 | 1.14.7 |
508-
509- Here `v1.8.x` means the "latest patch release of the v1.8 branch".
497+ | Image Name | v1.10 release branch version |
498+ |--------------------------------------------|------------------------------|
499+ | k8s.gcr.io/kube-apiserver-${ARCH} | v1.10.x |
500+ | k8s.gcr.io/kube-controller-manager-${ARCH} | v1.10.x |
501+ | k8s.gcr.io/kube-scheduler-${ARCH} | v1.10.x |
502+ | k8s.gcr.io/kube-proxy-${ARCH} | v1.10.x |
503+ | k8s.gcr.io/etcd-${ARCH} | 3.1.12 |
504+ | k8s.gcr.io/pause-${ARCH} | 3.1 |
505+ | k8s.gcr.io/k8s-dns-sidecar-${ARCH} | 1.14.8 |
506+ | k8s.gcr.io/k8s-dns-kube-dns-${ARCH} | 1.14.8 |
507+ | k8s.gcr.io/k8s-dns-dnsmasq-nanny-${ARCH} | 1.14.8 |
508+ | coredns/coredns | 1.0.6 |
509+
510+ Here `v1.10.x` means the "latest patch release of the v1.10 branch".
510511
511512`${ARCH}` can be one of : ` amd64` , `arm`, `arm64`, `ppc64le` or `s390x`.
512513
513514If you run Kubernetes version 1.10 or earlier, and if you set `--feature-gates=CoreDNS=true`,
514- you must also use the image `coredns/coredns:1.0.2` , instead of the three `k8s-dns-*` images.
515+ you must also use the `coredns/coredns` image , instead of the three `k8s-dns-*` images.
515516
516517In Kubernetes 1.11 and later, you can list and pull the images using the `kubeadm config images` sub-command :
517518` ` `
518519kubeadm config images list
519520kubeadm config images pull
520521` ` `
521522
523+ Starting with Kubernetes 1.12, the `k8s.gcr.io/kube-*`, `k8s.gcr.io/etcd` and `k8s.gcr.io/pause` images
524+ don't require an `-${ARCH}` suffix.
525+
522526# ## Automating kubeadm
523527
524528Rather than copying the token you obtained from `kubeadm init` to each node, as
0 commit comments