Merge pull request #4272 from luxas/kubeadm_upgrade_notice

Update some wording on kubeadm upgrades

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 %}

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 <DESIRED_VERSION>
 
    For instance, if you want to upgrade to `1.7.0`, you would run: