upgrades.md

Upgrading Kubernetes in Kubespray

Description

Kubespray handles upgrades the same way it handles initial deployment. That is to say that each component is laid down in a fixed order. You should be able to upgrade from Kubespray tag 2.0 up to the current master without difficulty. You can also individually control versions of components by explicitly defining their versions. Here are all version vars for each component:

• docker_version
• kube_version
• etcd_version
• calico_version
• calico_cni_version
• weave_version
• flannel_version
• kubedns_version

Unsafe upgrade example

If you wanted to upgrade just kube_version from v1.4.3 to v1.4.6, you could deploy the following way:

ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.4.3

And then repeat with v1.4.6 as kube_version:

ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.4.6

Graceful upgrade