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

Updating Ubuntu based instructions and upgrades

Browse Source
This commit is contained in:
Marco Ceppi
2017-05-02 07:59:24 -04:00
committed by Andrew Chen
parent e95cac7597
commit a5fa73e180
5 changed files with 46 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started-guides/ubuntu/upgrades.md
+24 -3
View File
@@ -7,7 +7,7 @@ This page will outline how to manage and execute a Kubernetes upgrade.
{% endcapture %}
{% capture prerequisites %}
This page assumes you have a working Juju deployed cluster.
This page assumes you have a working deployed cluster.
## Assumptions
@@ -27,10 +27,21 @@ Backing up etcd requires an export and snapshot, refer to the [backup documentat
juju upgrade-charm etcd
This will handle upgrades between minor versions of etcd. Major upgrades from etcd 2.x to 3.x are currently unsupported. Upgrade viability will be investigated when etcd 3.0 is finalized.
This will handle upgrades between minor versions of etcd. Major upgrades from etcd 2.x to 3.x are currently unsupported. Instead, data will be run in etcdv2 stores over the etcdv3 api.
# Upgrade Kubernetes
The Kubernetes Charms use snap channels to drive payloads. The channels are defined by `X.Y/channel` where `X.Y` is the `major.minor` release of Kubernetes (e.g. 1.6) and `channel` is one of the four following channels:
| Channel name | Description |
| ------------------- | ------------ |
| stable | The latest stable released patch version of Kubernetes |
| candidate | Release candidate releases of Kubernetes |
| beta | Latest alpha or beta of Kubernetes for that minor release |
| edge | Nightly builds of that minor release of Kubernetes |
If a release isn't available, the next highest channel is used. For example, 1.6/beta will load `/candidate` or `/stable` depending on availablility of release. Development versions of Kubernetes are available in that minor releases edge channel. There is no guarantee that edge or master will work with the current charms.
## Master Upgrades
First you need to upgrade the masters:
@@ -39,6 +50,13 @@ First you need to upgrade the masters:
NOTE: Always upgrade the masters before the workers.
Once the latest charm is deployed, the channel for Kubernetes can be selected by issuing the following:
juju config kubernetes-master channel=1.x/stable
Where `x` is the minor version of Kubernetes. For example, `1.6/stable`. See above for Channel definitions
## Worker Upgrades
Two methods of upgrading workers are supported. [Blue/Green Deployment](http://martinfowler.com/bliki/BlueGreenDeployment.html) and upgrade-in-place. Both methods are provided for operational flexibility and both are supported and tested. Blue/Green will require more hardware up front than inplace, but is a safer upgrade route.
@@ -66,6 +84,9 @@ Tear down old workers with:
## In place worker upgrade
juju upgrade-charm kubernetes-worker
juju config kubernetes-worker channel=1.x/stable
Where `x` is the minor version of Kubernetes. For example, `1.6/stable`. See above for Channel definitions
# Verify upgrade
@@ -94,4 +115,4 @@ At this time rolling back etcd is unsupported.
At this time rolling back Kubernetes is unsupported.
{% endcapture %}
{% include templates/task.md %}
{% include templates/task.md %}