From ba746446d2ecf9f04a37d98a735ddb1e2f51ed03 Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Tue, 31 Jul 2018 19:51:40 +0300 Subject: [PATCH] kubeadm-upgrade-1.11: fix wrong flag for feature gates (#9619) --- .../tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11.md b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11.md index 821d0631c6..8b4a2ec130 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11.md @@ -22,7 +22,7 @@ This page explains how to upgrade a Kubernetes cluster created with `kubeadm` fr - All containers are restarted after upgrade, because the container spec hash value is changed. - You can upgrade only froom one minor version to the next minor version. That is, you cannot skip versions when you upgrade. For example, you can upgrade only from 1.10 to 1.11, not from 1.9 to 1.11. - The default DNS provider in version 1.11 is [CoreDNS](https://coredns.io/) rather than [kube-dns](https://github.com/kubernetes/dns). -To keep `kube-dns`, pass `--feature-flags=CoreDNS=false` to `kubeadm upgrade apply`. +To keep `kube-dns`, pass `--feature-gates=CoreDNS=false` to `kubeadm upgrade apply`. {{% /capture %}} @@ -98,7 +98,7 @@ To keep `kube-dns`, pass `--feature-flags=CoreDNS=false` to `kubeadm upgrade app kubeadm upgrade apply v1.11.0 ``` - If you currently use `kube-dns` and wish to continue doing so, add `--feature-flags=CoreDNS=false`. + If you currently use `kube-dns` and wish to continue doing so, add `--feature-gates=CoreDNS=false`. You should see output similar to this: