From ed9af72c6fdb0e00b4a58ea64239dfaa95122992 Mon Sep 17 00:00:00 2001 From: Mark Janssen Date: Fri, 1 Jun 2018 00:45:57 +0200 Subject: [PATCH] Document using a custom CoreDNS image repository (#8574) --- content/en/docs/tasks/administer-cluster/coredns.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/en/docs/tasks/administer-cluster/coredns.md b/content/en/docs/tasks/administer-cluster/coredns.md index f860b64cdf..47ae3152e6 100644 --- a/content/en/docs/tasks/administer-cluster/coredns.md +++ b/content/en/docs/tasks/administer-cluster/coredns.md @@ -31,6 +31,15 @@ kubeadm init --feature-gates=CoreDNS=true This installs CoreDNS instead of kube-dns. +## Using a custom CoreDNS image repository with kubeadm + +To use a custom image repository for the CoreDNS image, e.g. one located in your own Docker registry, +you can execute the following command after kubeadm has deployed the CoreDNS manifest: + +```shell +kubectl set image -n kube-system deploy/coredns coredns=prefix.example.com/coredns/coredns:1.0.6 +``` + ## Upgrading an Existing Cluster with kubeadm In Kubernetes 1.10, you can also move to CoreDNS when you use `kubeadm` to upgrade