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

Update upgrades.md (#7333)

Browse Source 
* Update upgrades.md

Changed "Node:" to "Note:" because it was a note :)
Also a few minor changes for clarification.

* Revert flannel sentence
This commit is contained in:
Martin Mosegaard Amdisen
2018-02-12 16:06:48 +01:00
committed by k8s-ci-robot
parent f3cbfa347a
commit 883934fe7d
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/ubuntu/upgrades.md
+10 -10
View File
@@ -3,7 +3,7 @@ title: Upgrades
---
{% capture overview %}
This page will outline how to manage and execute a Kubernetes upgrade.
This page will outline how to manage and execute a Kubernetes upgrade.
{% endcapture %}
{% capture prerequisites %}
@@ -45,7 +45,7 @@ There may be an upgrade available for kubernetes, etcd, or both.
Backing up etcd requires an export and snapshot, refer to the
[backup documentation](/docs/getting-started-guides/ubuntu/backups) to create a snapshot.
After the snapshot upgrade the etcd service with:
After the snapshot, upgrade the etcd service with:
juju upgrade-charm etcd
@@ -72,11 +72,11 @@ There is no guarantee that edge snaps will work with the current charms.
### Master Upgrades
First you need to upgrade the masters:
First you need to upgrade the masters:
juju upgrade-charm kubernetes-master
**Node:** Always upgrade the masters before the workers.
**Note:** Always upgrade the masters before the workers.
{: .note}
Once the latest charm is deployed, the channel for Kubernetes can be selected by issuing the following:
@@ -102,19 +102,19 @@ but is a safer upgrade route.
Given a deployment where the workers are named kubernetes-alpha.
Deploy new worker(s):
Deploy new workers:
juju deploy kubernetes-beta
Pause the old workers so your workload migrates:
Pause the old workers so your workload migrates:
juju run-action kubernetes-alpha/# pause
Verify old workloads have migrated with:
Verify old workloads have migrated with:
kubectl get pod -o wide
Tear down old workers with:
Tear down old workers with:
juju remove-application kubernetes-alpha
@@ -133,7 +133,7 @@ run the upgrade action on each worker:
### Verify upgrade
`kubectl version` should return the newer version.
`kubectl version` should return the newer version.
It is recommended to rerun a [cluster validation](/docs/getting-started-guides/ubuntu/validation)
to ensure that the cluster upgrade has successfully completed.
@@ -141,7 +141,7 @@ to ensure that the cluster upgrade has successfully completed.
### Upgrade Flannel
Upgrading flannel can be done at any time, it is independent of Kubernetes upgrades.
Be advised that networking is interrupted during the upgrade. You can initiate a flannel upgrade:
Be advised that networking is interrupted during the upgrade. You can initiate a flannel upgrade with:
juju upgrade-charm flannel