remove 2.11 and 2.7 2.8 fro mcontrol plane upgrade

Author: ozRunAI

docs/admin/runai-setup/self-hosted/k8s/upgrade.md

@@ -36,33 +36,7 @@ If you are installing an air-gapped version of Run:ai, The Run:ai tar file conta
 
 Before proceeding with the upgrade, it's crucial to apply the specific prerequisites associated with your current version of Run:ai and every version in between up to the version you are upgrading to.
 
-### Upgrade from version 2.7 or 2.8
-
-Before upgrading the control plane, run: 
-
-``` bash
-POSTGRES_PV=$(kubectl get pvc pvc-postgresql -n runai-backend -o jsonpath='{.spec.volumeName}')
-THANOS_PV=$(kubectl get pvc pvc-thanos-receive -n runai-backend -o jsonpath='{.spec.volumeName}')
-kubectl patch pv $POSTGRES_PV $THANOS_PV -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'
-
-kubectl delete secret -n runai-backend runai-backend-postgresql
-kubectl delete sts -n runai-backend keycloak runai-backend-postgresql
-```
-
-Before version 2.9, the Run:ai installation, by default, included NGINX. It was possible to disable this installation. If NGINX is enabled in your current installation, as per the default, run the following 2 lines:
-
-``` bash
-kubectl delete ValidatingWebhookConfiguration runai-backend-nginx-ingress-admission
-kubectl delete ingressclass nginx 
-```
-(If Run:ai configuration has previously disabled NGINX installation then these lines should not be run).
-
-Next, install NGINX as described [here](../../cluster-setup/cluster-prerequisites.md#ingress-controller)
-
-Then create a TLS secret and upgrade the control plane as described in the [control plane installation](backend.md). Before upgrading, find customizations and merge them as discussed below. 
-
-
-### Upgrade from version 2.9, 2.10 , or 2.11 
+### Upgrade from version 2.9 
 
 Two significant changes to the control-plane installation have happened with version 2.12: _PVC ownership_ and _installation customization_. 
 
@@ -114,7 +88,7 @@ The Run:ai control-plane installation has been rewritten and is no longer using
     helm upgrade runai-backend control-plane-<NEW-VERSION>.tgz -n runai-backend  -f runai_control_plane_values.yaml --reset-then-reuse-values
     ```
 
-### Upgrade from version 2.7, 2.8, 2.9, or 2.11
+### Upgrade from version 2.9
 
 * Create a `tls secret` as described in the [control plane installation](backend.md). 
 * Upgrade the control plane as described in the [control plane installation](backend.md). During the upgrade, you must tell the installation __not__ to create the two PVCs:
@@ -141,4 +115,5 @@ The Run:ai control-plane installation has been rewritten and is no longer using
     ```
 
 ## Upgrade Cluster 
+
 To upgrade the cluster follow the instructions [here](../../cluster-setup/cluster-upgrade.md).

docs/admin/runai-setup/self-hosted/ocp/upgrade.md

@@ -2,23 +2,19 @@
 title: Upgrade self-hosted OpenShift installation
 ---
 # Upgrade Run:ai 
-
-
 !!! Important
     Run:ai data is stored in Kubernetes persistent volumes (PVs). Prior to Run:ai 2.12, PVs are owned by the Run:ai installation. Thus, uninstalling the `runai-backend` helm chart may delete all of your data. 
 
     From version 2.12 forward, PVs are owned the customer and are independent of the Run:ai installation. As such, they are subject to storage class [reclaim](https://kubernetes.io/docs/concepts/storage/storage-classes/#reclaim-policy){target=_blank} policy.
 
 ## Preparations
-
 ### Helm
 Run:ai requires [Helm](https://helm.sh/){target=_blank} 3.14 or later.
 Before you continue, validate your installed helm client version.
 To install or upgrade Helm, see [Installing Helm](https://helm.sh/docs/intro/install/){target=_blank}.
 If you are installing an air-gapped version of Run:ai, The Run:ai tar file contains the helm binary. 
 
 ### Software files
-
 === "Connected"
     Run the helm command below:
 
@@ -32,11 +28,8 @@ If you are installing an air-gapped version of Run:ai, The Run:ai tar file conta
     * Upload the images as described [here](preparations.md#software-artifacts).
 
 ## Before upgrade
-
 Before proceeding with the upgrade, it's crucial to apply the specific prerequisites associated with your current version of Run:ai and every version in between up to the version you are upgrading to.
 
-### Upgrade from version 2.7 or 2.8
-
 Before upgrading the control plane, run: 
 
 ``` bash
@@ -49,11 +42,10 @@ kubectl delete sts -n runai-backend keycloak runai-backend-postgresql
 
 Then upgrade the control plane as described [below](#upgrade-control-plane). Before upgrading, find customizations and merge them as discussed below. 
 
-### Upgrade from version 2.9, 2.10 or 2.11
-
+### Upgrade from version 2.9
 Two significant changes to the control-plane installation have happened with version 2.12: _PVC ownership_ and _installation customization_. 
-#### PVC ownership
 
+#### PVC ownership
 Run:ai will no longer directly create the PVCs that store Run:ai data (metrics and database). Instead, going forward, 
 
 * Run:ai requires a Kubernetes storage class to be installed.
@@ -68,17 +60,14 @@ kubectl patch pvc -n runai-backend pvc-postgresql  -p '{"metadata": {"annotation
 ```
 
 #### Installation customization
-
 The Run:ai control-plane installation has been rewritten and is no longer using a _backend values file_. Instead, to customize the installation use standard `--set` flags. If you have previously customized the installation, you must now extract these customizations and add them as `--set` flag to the helm installation:
 
 * Find previous customizations to the control plane if such exist. Run:ai provides a utility for that here `https://raw.githubusercontent.com/run-ai/docs/v2.13/install/backend/cp-helm-vals-diff.sh`. For information on how to use this utility please contact Run:ai customer support. 
 * Search for the customizations you found in the [optional configurations](./backend.md#additional-runai-configurations-optional) table and add them in the new format.  
 
 
 ## Upgrade Control Plane
-
 ### Upgrade from version 2.13, or later
-
 === "Connected"
 
     ``` bash
@@ -92,7 +81,7 @@ The Run:ai control-plane installation has been rewritten and is no longer using
     helm upgrade runai-backend control-plane-<NEW-VERSION>.tgz -n runai-backend  -f runai_control_plane_values.yaml --reset-then-reuse-values
     ```
 
-### Upgrade from version 2.7, 2.8, 2.9, or 2.11
+### Upgrade from version 2.9
 
 === "Connected"