whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update some wording on kubeadm upgrades

Browse Source
This commit is contained in:
Lucas Käldström
2017-07-05 21:59:14 +03:00
parent 30fd81db49
commit 5f52c69f9a
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/setup/independent/create-cluster-kubeadm.md
+2 -3
View File
@@ -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 not to change command line flags and break that flow. Other parts of the
experience are still under active development. Specifically, kubeadm relies on experience are still under active development. Specifically, kubeadm relies on
some features (bootstrap tokens, cluster signing), that are still considered 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 upgrades and high availability (HA). Any commands under `kubeadm alpha` (not
documented here) are, of course, alpha. documented here) are, of course, alpha.
**Be sure to read the [limitations](#limitations)**. Specifically, configuring **Be sure to read the [limitations](#limitations)**. Specifically, configuring
cloud providers is difficult. Upgrades are also not well documented or cloud providers is difficult.
particularly easy.
{% endcapture %} {% endcapture %}
{% capture prerequisites %} {% capture prerequisites %}
docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md
+4
View File
@@ -57,6 +57,10 @@ You need to have a Kubernetes cluster running version 1.6.x.
4. Perform kubeadm upgrade. 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> sudo kubeadm init --skip-preflight-checks --kubernetes-version <DESIRED_VERSION>
For instance, if you want to upgrade to `1.7.0`, you would run: For instance, if you want to upgrade to `1.7.0`, you would run: