Merge pull request #6894 from dixudx/upgrade_container_hash_change

add container restart caution when doing upgrade to 1.9
2018-01-09 11:56:03 -05:00
parent 2e6c14a47a e35c57785a
commit d45d3d750b
1 changed files with 3 additions and 0 deletions
@@ -23,6 +23,9 @@ Before proceeding:
 - `kubeadm upgrade` now allows you to upgrade etcd. `kubeadm upgrade` will also upgrade of etcd to 3.1.10 as part of upgrading from v1.8 to v1.9 by default. This is due to the fact that etcd 3.1.10 is the officially validated etcd version for Kubernetes v1.9. The upgrade is handled automatically by kubeadm for you.
 - Note that `kubeadm upgrade` will not touch any of your workloads, only Kubernetes-internal components. As a best-practice you should back up what's important to you. For example, any app-level state, such as a database an app might depend on (like MySQL or MongoDB) must be backed up beforehand.

+**Caution:** All the containers will get restarted after the upgrade, due to container spec hash value gets changed.
+{: .caution}
+
 Also, note that only one minor version upgrade is supported. For example, you can only upgrade from 1.8 to 1.9, not from 1.7 to 1.9.

 {% endcapture %}