Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update some wording on kubeadm upgrades #4272

Merged
merged 1 commit into from
Jul 5, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/setup/independent/create-cluster-kubeadm.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 %}
Expand Down
4 changes: 4 additions & 0 deletions docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggested edit: "This is a limitation we plan to address in v1.8."

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:
Expand Down