From 5f52c69f9aa858056eeb81e78fbddeb8443df911 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lucas=20K=C3=A4ldstr=C3=B6m?= Date: Wed, 5 Jul 2017 21:59:14 +0300 Subject: [PATCH] Update some wording on kubeadm upgrades --- docs/setup/independent/create-cluster-kubeadm.md | 5 ++--- docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md | 4 ++++ 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index f5eef552d3..bb7180128e 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -53,13 +53,12 @@ The experience for the command line is currently in beta and we are trying hard not to change command line flags and break that flow. Other parts of the experience are still under active development. Specifically, kubeadm relies on some features (bootstrap tokens, cluster signing), that are still considered -alpha. The implementation may change as the tool evolves to support easy +alpha. The implementation may change as the tool evolves to support even easier upgrades and high availability (HA). Any commands under `kubeadm alpha` (not documented here) are, of course, alpha. **Be sure to read the [limitations](#limitations)**. Specifically, configuring -cloud providers is difficult. Upgrades are also not well documented or -particularly easy. +cloud providers is difficult. {% endcapture %} {% capture prerequisites %} diff --git a/docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md b/docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md index 77475475db..ffdcec348d 100644 --- a/docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md +++ b/docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md @@ -57,6 +57,10 @@ You need to have a Kubernetes cluster running version 1.6.x. 4. Perform kubeadm upgrade. + **WARNING**: All parameters you passed to the first `kubeadm init` when you bootstrapped your + cluster **MUST** be specified here in the upgrade-`kubeadm init`-command. This is a limitation + we plan to address in v1.8. + sudo kubeadm init --skip-preflight-checks --kubernetes-version For instance, if you want to upgrade to `1.7.0`, you would run: