OPSEXP-2410 Add instruction to install with helm older version of ACS…

… on main helm readme (#1248)

Co-authored-by: Giovanni Toraldo <[email protected]>

docs/helm/README.md

@@ -285,6 +285,29 @@ There are also several [examples](../helm-examples.md) showing how to deploy wit
 * [Use a custom metadata keystore](https://alfresco.github.io/alfresco-helm-charts/charts/alfresco-repository/docs/keystores.html)
 * [Install ACS license as part of the deployment](https://alfresco.github.io/alfresco-helm-charts/charts/alfresco-repository/docs/enterprise-license.html)
 
+### Previous versions
+
+To install older versions of Alfresco, download the relevant values file from [this folder](https://github.com/Alfresco/acs-deployment/tree/master/helm/alfresco-content-services).
+Each file includes image tags that override the default tags, allowing you to
+deploy a specified ACS version. To deploy a particular ACS version, pass such
+file as an additional argument to the install command like the following:
+
+   ```bash
+   helm install acs alfresco/alfresco-content-services \
+     --values MAJOR.MINOR.N_values.yaml \
+     --atomic \
+     --timeout 10m0s \
+     --namespace alfresco
+   ```
+
+**NOTE:** Each values file is pre-configured with the latest supported component versions
+for the specified ACS major version. For example, the 7.4.N values file will
+deploy ACS version 7.4.2.3 alongside Alfresco Digital Workspace (ADW) version
+4.4.1. These configurations are recommended to ensure compatibility and
+stability across components. However, if a specific version of any component is
+needed, you can either edit the values file directly or override the version by
+adding the --set component.image.tag=x.y.z option to the Helm command.
+
 ## Upgrade
 
 You can use the standard `helm upgrade acs ./alfresco/alfresco-content-services

docs/helm/desktop-deployment.md

@@ -133,23 +133,7 @@ The `helm` command above installs the most current released version of ACS Enter
 
 #### Enterprise deployment for previous versions
 
-To deploy a previous version of ACS Enterprise follow the steps below.
-
-1. Download the version specific values file you require from [this folder](https://github.com/Alfresco/acs-deployment/tree/master/helm/alfresco-content-services)
-2. Deploying the specific version of ACS can be achieved by executing the following:
-
-   ```bash
-   helm install acs alfresco/alfresco-content-services \
-     --values MAJOR.MINOR.N_values.yaml \
-     --values local-dev_values.yaml \
-     --atomic \
-     --timeout 10m0s \
-     --namespace alfresco
-   ```
-
-> NOTE: The command will wait until the deployment is ready so please be
-patient. See below for
-[troubleshooting](#troubleshooting) tips.
+Use the above helm commands and pass an additional argument as described in this [section](./README.md#previous-versions).
 
 #### Development versions deployment
 

docs/helm/eks-deployment.md

@@ -630,24 +630,7 @@ helm upgrade --install acs alfresco/alfresco-content-services \
 
 #### Previous Enterprise Versions
 
-1. Download the version-specific values file you require from [this folder](https://github.com/Alfresco/acs-deployment/blob/master/helm/alfresco-content-services).
-
-Deploy the specific version of ACS by running the following command (replacing
-`YOUR-DOMAIN-NAME` with the hosted zone you created earlier and `MAJOR` &
-`MINOR` with the appropriate values):
-
-```sh
-helm upgrade --install acs alfresco/alfresco-content-services \
---values=MAJOR.MINOR.N_values.yaml \
---set alfresco-repository.persistence.enabled=true \
---set alfresco-repository.persistence.storageClass="nfs-client" \
---set alfresco-transform-service.filestore.persistence.enabled=true \
---set alfresco-transform-service.filestore.persistence.storageClass="nfs-client" \
---set global.known_urls=https://${ACS_HOSTNAME} \
---set global.alfrescoRegistryPullSecrets=quay-registry-secret \
---values letsencrypt_values.yaml \
---namespace=alfresco
-```
+Use the above helm commands and pass an additional argument as described in this [section](./README.md#previous-versions).
 
 ### Wait for successful deployment