From be5c7054490caa45168e33ca4d260a1de711ce52 Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Tue, 7 May 2024 14:59:21 +0200 Subject: [PATCH] Update docs/howto/upgrade-cluster/k8s-version-skew.md --- docs/howto/upgrade-cluster/k8s-version-skew.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/upgrade-cluster/k8s-version-skew.md b/docs/howto/upgrade-cluster/k8s-version-skew.md index 6a1279fc44..a2ec3f1e93 100644 --- a/docs/howto/upgrade-cluster/k8s-version-skew.md +++ b/docs/howto/upgrade-cluster/k8s-version-skew.md @@ -10,7 +10,7 @@ can _skew_ in relation to each other. When we upgrade, we are practically constrained by [Kubernetes' version skew policy] in the following ways: -1. Highly available clusters' control planes with can only be upgraded one minor +1. Highly available clusters' control planes can only be upgraded one minor version at the time (`api-server` requirement). All of our new clusters and most of our old clusters are regional, so our