From 85007fa9a7dee1cbb8761ed48ad7157b84cdf96d Mon Sep 17 00:00:00 2001 From: Kenichi Omichi Date: Mon, 15 Mar 2021 03:59:05 -0700 Subject: [PATCH] Update upgrades.md (#7361) upgrades.md explains how to do upgrade from v1.4.3 to v1.4.6 as an example. The versions are a little old, and the doc readers would have a concern the upgrade works fine or not. This updates versions after verifying the way works fine by hands. --- docs/upgrades.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/upgrades.md b/docs/upgrades.md index 15aac57fe..b325b619f 100644 --- a/docs/upgrades.md +++ b/docs/upgrades.md @@ -17,21 +17,21 @@ versions. Here are all version vars for each component: :warning: [Attempting to upgrade from an older release straight to the latest release is unsupported and likely to break something](https://github.com/kubernetes-sigs/kubespray/issues/3849#issuecomment-451386515) :warning: -See [Multiple Upgrades](#multiple-upgrades) for how to upgrade from older releases to the latest release +See [Multiple Upgrades](#multiple-upgrades) for how to upgrade from older Kubespray release to the latest release ## Unsafe upgrade example -If you wanted to upgrade just kube_version from v1.4.3 to v1.4.6, you could +If you wanted to upgrade just kube_version from v1.18.10 to v1.19.7, you could deploy the following way: ```ShellSession -ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.4.3 -e upgrade_cluster_setup=true +ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.18.10 -e upgrade_cluster_setup=true ``` -And then repeat with v1.4.6 as kube_version: +And then repeat with v1.19.7 as kube_version: ```ShellSession -ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.4.6 -e upgrade_cluster_setup=true +ansible-playbook cluster.yml -i inventory/sample/hosts.ini -e kube_version=v1.19.7 -e upgrade_cluster_setup=true ``` The var ```-e upgrade_cluster_setup=true``` is needed to be set in order to migrate the deploys of e.g kube-apiserver inside the cluster immediately which is usually only done in the graceful upgrade. (Refer to [#4139](https://github.com/kubernetes-sigs/kubespray/issues/4139) and [#4736](https://github.com/kubernetes-sigs/kubespray/issues/4736)) @@ -45,15 +45,15 @@ existing cluster. That means there must be at least 1 kube-master already deployed. ```ShellSession -ansible-playbook upgrade-cluster.yml -b -i inventory/sample/hosts.ini -e kube_version=v1.6.0 +ansible-playbook upgrade-cluster.yml -b -i inventory/sample/hosts.ini -e kube_version=v1.19.7 ``` After a successful upgrade, the Server Version should be updated: ```ShellSession $ kubectl version -Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0", GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37", GitTreeState:"clean", BuildDate:"2017-03-28T19:15:41Z", GoVersion:"go1.8", Compiler:"gc", Platform:"darwin/amd64"} -Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0+coreos.0", GitCommit:"8031716957d697332f9234ddf85febb07ac6c3e3", GitTreeState:"clean", BuildDate:"2017-03-29T04:33:09Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"} +Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"} +Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:15:20Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"} ``` If you want to manually control the upgrade procedure, you can use the variables `upgrade_node_confirm` or `upgrade_node_pause_seconds`: