From ae625a649f6c3421e34d61463d5d8fe66c9181d9 Mon Sep 17 00:00:00 2001 From: Peter Rifel Date: Thu, 9 Jan 2025 10:02:05 -0600 Subject: [PATCH] Add more details and update updates_and_upgrades.md --- docs/operations/updates_and_upgrades.md | 5 +++++ docs/tutorial/upgrading-kubernetes.md | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/operations/updates_and_upgrades.md b/docs/operations/updates_and_upgrades.md index 878b65bd6e6e2..1369e53eeef09 100644 --- a/docs/operations/updates_and_upgrades.md +++ b/docs/operations/updates_and_upgrades.md @@ -62,9 +62,14 @@ It is recommended to run the latest version of kOps to ensure compatibility with In future the upgrade step will likely perform the update immediately (and possibly even without a node restart), but currently you must: +For kOps 1.31 and newer, run `kops reconcile cluster $NAME --yes` + +For older kOps versions, run: * `kops update cluster $NAME` to preview, then `kops update cluster $NAME --yes` * `kops rolling-update cluster $NAME` to preview, then `kops rolling-update cluster $NAME --yes` +For more detail about the command change in kOps 1.31, see [docs/tutorial/upgrading-kubernetes.md](/docs/tutorial/upgrading-kubernetes.md). + Upgrade uses the latest Kubernetes version considered stable by kOps, defined in `https://github.com/kubernetes/kops/blob/master/channels/stable`. diff --git a/docs/tutorial/upgrading-kubernetes.md b/docs/tutorial/upgrading-kubernetes.md index fe564ff84f15a..0d126bb47a079 100644 --- a/docs/tutorial/upgrading-kubernetes.md +++ b/docs/tutorial/upgrading-kubernetes.md @@ -4,7 +4,7 @@ Kops' upgrade procedure has hostorically risked violating the [Kubelet version skew policy](https://kubernetes.io/releases/version-skew-policy/#kubelet). Between `kops update cluster --yes` and every kube-apiserver being rotated with `kops rolling-update cluster --yes`, newly launched nodes running new kubelet versions could be connecting to older `kube-apiserver` nodes. -**Violating this policy when upgrading to Kubernetes 1.31 can cause newer kubelets to crash.** +**Violating this policy when upgrading to Kubernetes 1.31 can cause newer kubelets to crash.** [This kubernetes issue](https://github.com/kubernetes/kubernetes/issues/127316) provides details though it was not addressed because the change does not actually violate the version skew policy, it merely breaks tooling that was already violating the policy. To upgrade a cluster to Kubernetes 1.31 or newer, use the new `kops reconcile cluster` command introduced in Kops 1.31. This replaces both `kops update cluster --yes` and `kops rolling-update cluster --yes`.