From bd1cfccef3781360019c8d5b5e02424631b06924 Mon Sep 17 00:00:00 2001 From: martyav Date: Fri, 17 Mar 2023 16:49:13 -0400 Subject: [PATCH 1/8] #487 Instructions for Preparing Hardened Imported/Custom RKE2/K3s Cluster for Upgrade from 1.24 to 1.25 --- ...upgrade-a-hardened-cluster-to-k8s-v1-25.md | 48 +++++++++++++++++++ .../rancher-psact.yaml | 37 ++++++++++++++ 2 files changed, 85 insertions(+) create mode 100644 docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md create mode 100644 docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-psact.yaml diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md new file mode 100644 index 00000000000..21cdb0f38ea --- /dev/null +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -0,0 +1,48 @@ +--- +title: Preparing to Upgrade a Hardened Custom/Imported Cluster to Kubernetes v1.25 +--- + +Kubernetes v1.25 changes how clusters describe and implement security policies. From this version forward, [Pod Security Policies (PSPs)](https://kubernetes.io/docs/concepts/security/pod-security-policy/) are no longer available. Kubernetes v1.25 replaces them with new security objects: [Pod Security Standards (PSS)](https://kubernetes.io/docs/concepts/security/pod-security-standards/), and [Pod Security Admissions (PSAs)](https://kubernetes.io/docs/concepts/security/pod-security-admission/). + +If you have custom or imported hardened clusters, you must make special preparations to ensure that the upgrade from an earlier version of Kubernetes to ≥v1.25 goes smoothly. + +## Upgrading Imported Hardened Clusters to Kubernetes ≥v1.25 + + + +1. Save [`rancher-psact.yaml`](./rancher-psact.yaml) in `/etc/rancher/rke2` on each node in the cluster. +1. Edit the RKE2 configuration file: + 1. Update the `profile` field to `cis-1.23`. + 1. Specify the path for the configuration file that you just added: `pod-security-admission-config-file: /etc/rancher/rke2/rancher-psact.yaml`. + +After you perform these steps, you can upgrade the cluster's Kubernetes version through the Rancher UI. + + +Follow the [official K3s instructions](https://docs.k3s.io/known-issues#:~:text=Upgrading%20Hardened%20Clusters%20from%20v1.24.x%20to%20v1.25.x), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. + +After you perform these steps, you can upgrade the cluster's Kubernetes version through the Rancher UI. + + + +## Upgrading Custom Hardened Clusters to Kubernetes ≥v1.25 + + + +1. In the upper left corner, click **☰ > Cluster Management**. +1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. +1. Select **Edit Config**. +1. Under **Basics > Security**, in the **CIS Profile** dropdown menu, select `cis-1.23`. +1. In the **Default Pod Security Admission** dropdown menu, select `rancher-restricted`. +1. Click **Save**. +1. Upgrade the cluster's Kubernetes version through the Rancher UI. + + +1. In the upper left corner, click **☰ > Cluster Management**. +1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. +1. Select **Edit YAML**. +1. Delete `PodSecurityPolicy` from `kube-apiserver-arg.enable-admission-plugins` +1. Add this line to the `spec` field: `defaultPodSecurityAdmissionConfigurationTemplateName: rancher-restricted` +1. Update `kubernetesVersion` to your chosen version (v1.25 or later). +1. Click **Save**. + + \ No newline at end of file diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-psact.yaml b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-psact.yaml new file mode 100644 index 00000000000..ae248cc9b7c --- /dev/null +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-psact.yaml @@ -0,0 +1,37 @@ +apiVersion: apiserver.config.k8s.io/v1 +kind: AdmissionConfiguration +plugins: +- configuration: + apiVersion: pod-security.admission.config.k8s.io/v1 + defaults: + audit: restricted + audit-version: latest + enforce: restricted + enforce-version: latest + warn: restricted + warn-version: latest + exemptions: + namespaces: + - ingress-nginx + - kube-system + - cattle-system + - cattle-epinio-system + - cattle-fleet-system + - longhorn-system + - cattle-neuvector-system + - cattle-monitoring-system + - rancher-alerting-drivers + - cis-operator-system + - cattle-csp-adapter-system + - cattle-externalip-system + - cattle-gatekeeper-system + - istio-system + - cattle-istio-system + - cattle-logging-system + - cattle-windows-gmsa-system + - cattle-sriov-system + - cattle-ui-plugin-system + - tigera-operator + kind: PodSecurityConfiguration + name: PodSecurity + path: "" \ No newline at end of file From 3c95c3bddac96ee292823429675c8755a092e0ef Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 20 Mar 2023 17:31:16 -0400 Subject: [PATCH 2/8] added instructions for updating K8s thru UI --- ...re-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md index 21cdb0f38ea..79622f00992 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -1,5 +1,5 @@ --- -title: Preparing to Upgrade a Hardened Custom/Imported Cluster to Kubernetes v1.25 +title: Upgrade a Hardened Custom/Imported Cluster to Kubernetes v1.25 --- Kubernetes v1.25 changes how clusters describe and implement security policies. From this version forward, [Pod Security Policies (PSPs)](https://kubernetes.io/docs/concepts/security/pod-security-policy/) are no longer available. Kubernetes v1.25 replaces them with new security objects: [Pod Security Standards (PSS)](https://kubernetes.io/docs/concepts/security/pod-security-standards/), and [Pod Security Admissions (PSAs)](https://kubernetes.io/docs/concepts/security/pod-security-admission/). @@ -14,16 +14,19 @@ If you have custom or imported hardened clusters, you must make special preparat 1. Edit the RKE2 configuration file: 1. Update the `profile` field to `cis-1.23`. 1. Specify the path for the configuration file that you just added: `pod-security-admission-config-file: /etc/rancher/rke2/rancher-psact.yaml`. - -After you perform these steps, you can upgrade the cluster's Kubernetes version through the Rancher UI. Follow the [official K3s instructions](https://docs.k3s.io/known-issues#:~:text=Upgrading%20Hardened%20Clusters%20from%20v1.24.x%20to%20v1.25.x), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. - -After you perform these steps, you can upgrade the cluster's Kubernetes version through the Rancher UI. +After you perform these steps, you can upgrade the cluster's Kubernetes version through the Rancher UI: + +1. In the upper left corner, click **☰ > Cluster Management**. +1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. +1. Select **Edit Config**. +1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. + ## Upgrading Custom Hardened Clusters to Kubernetes ≥v1.25 From 5235e2f42682dbea9ea55176dd60cdd483c57eb2 Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 20 Mar 2023 17:41:27 -0400 Subject: [PATCH 3/8] changed file name, added sidebar entry --- ...o-k8s-v1-25.md => upgrade-a-hardened-cluster-to-k8s-v1-25.md} | 0 sidebars.js | 1 + 2 files changed, 1 insertion(+) rename docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/{prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md => upgrade-a-hardened-cluster-to-k8s-v1-25.md} (100%) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md similarity index 100% rename from docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/prepare-to-upgrade-a-hardened-cluster-to-k8s-v1-25.md rename to docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md diff --git a/sidebars.js b/sidebars.js index 0728d8d6562..2125b29744b 100644 --- a/sidebars.js +++ b/sidebars.js @@ -115,6 +115,7 @@ const sidebars = { "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks", "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks", "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke", + "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md", "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting", ] }, From 2e13013f6bfdf96b2bcfb5790615328d2c802c0c Mon Sep 17 00:00:00 2001 From: martyav Date: Mon, 20 Mar 2023 18:01:52 -0400 Subject: [PATCH 4/8] one more set of steps added --- .../upgrade-a-hardened-cluster-to-k8s-v1-25.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md index 79622f00992..e8762ebcd49 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -37,7 +37,13 @@ After you perform these steps, you can upgrade the cluster's Kubernetes version 1. Under **Basics > Security**, in the **CIS Profile** dropdown menu, select `cis-1.23`. 1. In the **Default Pod Security Admission** dropdown menu, select `rancher-restricted`. 1. Click **Save**. -1. Upgrade the cluster's Kubernetes version through the Rancher UI. + +Now, upgrade the cluster's Kubernetes version through the Rancher UI: + +1. In the upper left corner, click **☰ > Cluster Management**. +1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. +1. Select **Edit Config**. +1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. 1. In the upper left corner, click **☰ > Cluster Management**. From 770d58ffb98a43cff99cf5a21a4ca00dd54e5dfc Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Tue, 21 Mar 2023 14:28:09 -0400 Subject: [PATCH 5/8] Apply suggestions from code review Co-authored-by: Billy Tat --- .../upgrade-a-hardened-cluster-to-k8s-v1-25.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md index e8762ebcd49..92febfb731d 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -4,19 +4,20 @@ title: Upgrade a Hardened Custom/Imported Cluster to Kubernetes v1.25 Kubernetes v1.25 changes how clusters describe and implement security policies. From this version forward, [Pod Security Policies (PSPs)](https://kubernetes.io/docs/concepts/security/pod-security-policy/) are no longer available. Kubernetes v1.25 replaces them with new security objects: [Pod Security Standards (PSS)](https://kubernetes.io/docs/concepts/security/pod-security-standards/), and [Pod Security Admissions (PSAs)](https://kubernetes.io/docs/concepts/security/pod-security-admission/). -If you have custom or imported hardened clusters, you must make special preparations to ensure that the upgrade from an earlier version of Kubernetes to ≥v1.25 goes smoothly. +If you have custom or imported hardened clusters, you must make special preparations to ensure that the upgrade from an earlier version of Kubernetes to v1.25 or later goes smoothly. ## Upgrading Imported Hardened Clusters to Kubernetes ≥v1.25 - + 1. Save [`rancher-psact.yaml`](./rancher-psact.yaml) in `/etc/rancher/rke2` on each node in the cluster. 1. Edit the RKE2 configuration file: 1. Update the `profile` field to `cis-1.23`. 1. Specify the path for the configuration file that you just added: `pod-security-admission-config-file: /etc/rancher/rke2/rancher-psact.yaml`. + -Follow the [official K3s instructions](https://docs.k3s.io/known-issues#:~:text=Upgrading%20Hardened%20Clusters%20from%20v1.24.x%20to%20v1.25.x), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. +Follow the official K3s instructions on [Upgrading Hardened Clusters from v1.24.x to v1.25.x](https://docs.k3s.io/known-issues#:~:text=Upgrading%20Hardened%20Clusters%20from%20v1.24.x%20to%20v1.25.x), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. @@ -27,9 +28,9 @@ After you perform these steps, you can upgrade the cluster's Kubernetes version 1. Select **Edit Config**. 1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. -## Upgrading Custom Hardened Clusters to Kubernetes ≥v1.25 +## Upgrading Custom Hardened Clusters to Kubernetes v1.25 or Later - + 1. In the upper left corner, click **☰ > Cluster Management**. 1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. @@ -44,6 +45,7 @@ Now, upgrade the cluster's Kubernetes version through the Rancher UI: 1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. 1. Select **Edit Config**. 1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. + 1. In the upper left corner, click **☰ > Cluster Management**. @@ -53,5 +55,6 @@ Now, upgrade the cluster's Kubernetes version through the Rancher UI: 1. Add this line to the `spec` field: `defaultPodSecurityAdmissionConfigurationTemplateName: rancher-restricted` 1. Update `kubernetesVersion` to your chosen version (v1.25 or later). 1. Click **Save**. + \ No newline at end of file From bbd1595d87b43bd882fef9c57f94ce4eeb04587e Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Tue, 21 Mar 2023 15:49:48 -0400 Subject: [PATCH 6/8] Apply suggestions from code review Co-authored-by: Jiaqi Luo <6218999+jiaqiluo@users.noreply.github.com> Co-authored-by: Billy Tat --- ...upgrade-a-hardened-cluster-to-k8s-v1-25.md | 27 ++++++++++--------- sidebars.js | 2 +- 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md index 92febfb731d..b938da78013 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -6,17 +6,22 @@ Kubernetes v1.25 changes how clusters describe and implement security policies. If you have custom or imported hardened clusters, you must make special preparations to ensure that the upgrade from an earlier version of Kubernetes to v1.25 or later goes smoothly. -## Upgrading Imported Hardened Clusters to Kubernetes ≥v1.25 +## Upgrading Imported Hardened Clusters to Kubernetes v1.25 or Later -1. Save [`rancher-psact.yaml`](./rancher-psact.yaml) in `/etc/rancher/rke2` on each node in the cluster. + +Perform the following on each node in the cluster: +1. Save [`rancher-psact.yaml`](./rancher-psact.yaml) in `/etc/rancher/rke2`. 1. Edit the RKE2 configuration file: - 1. Update the `profile` field to `cis-1.23`. - 1. Specify the path for the configuration file that you just added: `pod-security-admission-config-file: /etc/rancher/rke2/rancher-psact.yaml`. + 1. Update the `profile` field to `cis-1.23`. + 1. Specify the path for the configuration file that you just added: `pod-security-admission-config-file: /etc/rancher/rke2/rancher-psact.yaml`. + +Perform the following on each node in the cluster: + Follow the official K3s instructions on [Upgrading Hardened Clusters from v1.24.x to v1.25.x](https://docs.k3s.io/known-issues#:~:text=Upgrading%20Hardened%20Clusters%20from%20v1.24.x%20to%20v1.25.x), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. @@ -30,24 +35,20 @@ After you perform these steps, you can upgrade the cluster's Kubernetes version ## Upgrading Custom Hardened Clusters to Kubernetes v1.25 or Later - + + 1. In the upper left corner, click **☰ > Cluster Management**. 1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. 1. Select **Edit Config**. 1. Under **Basics > Security**, in the **CIS Profile** dropdown menu, select `cis-1.23`. 1. In the **Default Pod Security Admission** dropdown menu, select `rancher-restricted`. +1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. 1. Click **Save**. -Now, upgrade the cluster's Kubernetes version through the Rancher UI: - -1. In the upper left corner, click **☰ > Cluster Management**. -1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. -1. Select **Edit Config**. -1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. - - + + 1. In the upper left corner, click **☰ > Cluster Management**. 1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. 1. Select **Edit YAML**. diff --git a/sidebars.js b/sidebars.js index 2125b29744b..dbaf0f24298 100644 --- a/sidebars.js +++ b/sidebars.js @@ -115,7 +115,7 @@ const sidebars = { "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks", "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks", "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke", - "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md", + "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25", "getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting", ] }, From c2381be8900a4dda20e22b4c2803f27a9fd5d74f Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Tue, 21 Mar 2023 17:03:32 -0400 Subject: [PATCH 7/8] Apply suggestions from code review Co-authored-by: Billy Tat --- .../upgrade-a-hardened-cluster-to-k8s-v1-25.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md index b938da78013..0edd655e7d2 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -22,7 +22,7 @@ Perform the following on each node in the cluster: Perform the following on each node in the cluster: -Follow the official K3s instructions on [Upgrading Hardened Clusters from v1.24.x to v1.25.x](https://docs.k3s.io/known-issues#:~:text=Upgrading%20Hardened%20Clusters%20from%20v1.24.x%20to%20v1.25.x), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. +Follow the official K3s instructions on [Upgrading Hardened Clusters from v1.24.x to v1.25.x](https://docs.k3s.io/known-issues#hardened-125), but use a [custom](./rancher-psact.yaml) Rancher PSA configuration template, instead of the configuration provided on the official K3s site. From 9ea3c3640a17dc27abdd341719cc7cf51c332d76 Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Tue, 21 Mar 2023 17:18:55 -0400 Subject: [PATCH 8/8] Update docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md Co-authored-by: Billy Tat --- .../upgrade-a-hardened-cluster-to-k8s-v1-25.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md index 0edd655e7d2..84a9ead87af 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrade-a-hardened-cluster-to-k8s-v1-25.md @@ -32,6 +32,7 @@ After you perform these steps, you can upgrade the cluster's Kubernetes version 1. Find the cluster you want to update in the **Clusters** table, and click the **⋮**. 1. Select **Edit Config**. 1. In the **Kubernetes Version** dropdown menu, select the version that you would like to use. +1. Click **Save**. ## Upgrading Custom Hardened Clusters to Kubernetes v1.25 or Later