From 5e906cb0b9e59c539c5b8dd4c5f3ba061023b681 Mon Sep 17 00:00:00 2001 From: eskild <42120229+iameskild@users.noreply.github.com> Date: Tue, 26 Sep 2023 12:53:16 -0700 Subject: [PATCH] Update docs/docs/how-tos/upgrade-kubernetes-version.md Co-authored-by: Pavithra Eswaramoorthy --- docs/docs/how-tos/upgrade-kubernetes-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-tos/upgrade-kubernetes-version.md b/docs/docs/how-tos/upgrade-kubernetes-version.md index dbfa75109..2fca3fd35 100644 --- a/docs/docs/how-tos/upgrade-kubernetes-version.md +++ b/docs/docs/how-tos/upgrade-kubernetes-version.md @@ -18,7 +18,7 @@ The Nebari development team tries to stay ahead of this by supporting the latest This `HIGHEST_SUPPORTED_K8S_VERSION` is, at times, a minor version or two behind the officially released Kubernetes version. ::: -Many cloud providers enable users to automatically upgrade their Kubernetes cluster (control plane), however given the potential for deprecations and other changes, Nebari deployed to these cloud have this feature automatically disabled. +Many cloud providers enable users to automatically upgrade their Kubernetes cluster (control plane), however given the potential for deprecations and other changes, Nebari deployed to these clouds has this feature automatically disabled. This upgrade process bumps the version of the control plane along with all node groups.