Merge pull request #795 from entando/ENDOC-757-update7.3

ENDOC-757-update7.3

vuepress/docs/next/docs/getting-started/README.md

@@ -17,7 +17,7 @@ The following steps launch an Ubuntu VM via Multipass, install Kubernetes, then
 
 2. Install Entando into Kubernetes on Ubuntu using the [Entando CLI](entando-cli.md)
 
-<EntandoCode> curl -sL "https://get.entando.org" | ENTANDO_RELEASE="{{ $site.themeConfig.entando.fixpack.v72 }}" bash
+<EntandoCode> curl -sL "https://get.entando.org" | ENTANDO_RELEASE="{{ $site.themeConfig.entando.fixpack.v73 }}" bash
 </EntandoCode>
 
 3. The progress of the install is displayed on the console. Installation can take up to 10 minutes, depending on how long the Docker images take to download. The sequence of steps performed by the CLI is identical to the manual steps below. To understand what the CLI does, review the manual steps.
@@ -157,12 +157,12 @@ From your Ubuntu shell
 
 1. Install the cluster-scoped custom resource definitions (CRDs)
 
-<EntandoCode>sudo kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
+<EntandoCode>sudo kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
 </EntandoCode>
 
 2. Install the namespace-scoped custom resources
 
-<EntandoCode>sudo kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
+<EntandoCode>sudo kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
 
 #### Configure Access to Your Cluster
 
@@ -186,7 +186,7 @@ Now that you've determined YOUR-HOST-NAME, use it to configure the Entando Appli
 
 1. Download the template `entando-app.yaml`.
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
 
 2. Modify `entando-app.yaml` to set the `ingressHostName` to YOUR-HOST-NAME. Examples:
 - `ingressHostName`: quickstart.mshome.net

vuepress/docs/next/docs/getting-started/entando-cli.md

@@ -29,7 +29,7 @@ The basic requirements for the CLI vary with use case, as shown in the table bel
 ## Install the CLI
 Install the current official release of the CLI:
 
-<EntandoCode> bash <(curl -L "https://get.entando.org/cli") --update --release="{{ $site.themeConfig.entando.fixpack.v72 }}" </EntandoCode>
+<EntandoCode> bash <(curl -L "https://get.entando.org/cli") --update --release="{{ $site.themeConfig.entando.fixpack.v73 }}" </EntandoCode>
 
 >The automatic option in [Getting Started](../getting-started/) will install the CLI along with a quickstart Entando Application.
 
@@ -121,7 +121,7 @@ The `ent quickstart` command accepts parameters to customize your quickstart env
 |Operation |Syntax|Description|
 |:--|:--|:--|
 |ent quickstart| ent quickstart --vm-reuse=YOUR-EXISTING-VM| Reuse an existing VM
-||ent quickstart --release="{{ $site.themeConfig.entando.fixpack.v72 }}" | Use a specific release version for the install
+||ent quickstart --release="{{ $site.themeConfig.entando.fixpack.v73 }}" | Use a specific release version for the install
 
 
 ## Reference

vuepress/docs/next/docs/reference/local-tips-and-tricks.md

@@ -27,7 +27,7 @@ ent kubectl delete namespace entando
 
 2. Run the following command
 
-<EntandoCode>ent quickstart "entando" "quickstart" --simple --debug=1 --yes --with-vm --release={{ $site.themeConfig.entando.fixpack.v72 }}
+<EntandoCode>ent quickstart "entando" "quickstart" --simple --debug=1 --yes --with-vm --release={{ $site.themeConfig.entando.fixpack.v73 }}
 </EntandoCode>
 
 The namespace will be recreated, preserving the images already pulled, so it's unlikely the installation time will exceed the timeout threshold again.

vuepress/docs/next/tutorials/consume/cds.md

@@ -15,7 +15,7 @@ A set of resources are necessary to separate the storage and user data for the p
 2. Click on `Public Key` for `rsa-generated` provider and copy the content. This will be `YOUR-PUBLIC-KEYCLOAK-KEY` below.
 3. Download the template `entando-cds.yaml`:
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-cds.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-cds.yaml"</EntandoCode>
 
 4. Replace the placeholders in `entando-cds.yaml` with the appropriate values for your environment. 
 

vuepress/docs/next/tutorials/consume/entando-operator.md

@@ -14,7 +14,7 @@ kubectl get configmap -n entando
 ## Add a new ConfigMap
 If the ConfigMap doesn't already exist, you can use a template as a starting point.
 
-<EntandoCode>curl -sfL "https://raw.githubusercontent.com/entando/entando-releases/{{$site.themeConfig.entando.fixpack.v72}}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
+<EntandoCode>curl -sfL "https://raw.githubusercontent.com/entando/entando-releases/{{$site.themeConfig.entando.fixpack.v73}}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
 
 Edit `entando-operator-config.yaml` to adjust existing settings or add new ones. You can then apply it to Kubernetes.
 

vuepress/docs/next/tutorials/consume/solr.md

@@ -30,7 +30,7 @@ helm install solr-operator apache-solr/solr-operator --version 0.5.0
 ```
 4. Download the template `entando-solrCloud.yaml`. Adjust the resource settings such as memory, CPU, storage, or replicas using this file.
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-solrCloud.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-solrCloud.yaml"</EntandoCode>
 
 5. Create the Solr application resources:
 ``` bash

vuepress/docs/next/tutorials/getting-started/azure-install.md

@@ -78,7 +78,7 @@ See the [Install Guide for NGINX on Azure](https://kubernetes.github.io/ingress-
 
 1. Apply the cluster-scoped custom resource definitions (CRDs). This is required only once per cluster.
 
-<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
+<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
 </EntandoCode>
 
 2. Create the namespace for the Entando Application
@@ -87,7 +87,7 @@ kubectl create namespace entando
 ```
 3. Download the `entando-operator-config` template so you can configure the [Entando Operator](../consume/entando-operator.md) 
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
 
 4. Edit the `entando-operator-config.yaml` to add two properties
 ```yaml
@@ -103,7 +103,7 @@ kubectl apply -f entando-operator-config.yaml -n entando
 
 6. Apply the namespace-scoped custom resources
 
-<EntandoCode>kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
+<EntandoCode>kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
 
 
 7. You can use `kubectl get pods -n entando --watch` to see the initial pods start up. Use `Ctrl+C` to exit.
@@ -117,7 +117,7 @@ entando-operator-5b5465788b-ghb25      1/1     Running   0          5m53s
 ### Configure the Entando Application
 1. Download the `entando-app.yaml` template
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
 
 2. Edit `entando-app.yaml`. Replace `YOUR-HOST-NAME` with `EXTERNAL-IP` + `.nip.io`. See [the EntandoApp custom resource overview](../../docs/reference/entandoapp-cr.md) for additional options.
 ```yaml

vuepress/docs/next/tutorials/getting-started/eks-install.md

@@ -153,7 +153,7 @@ See the [NGINX AWS Guide](https://kubernetes.github.io/ingress-nginx/deploy/#aws
 
 1. Apply the cluster-scoped custom resource definitions (CRDs). This is required only once per cluster.
 
-<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
+<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
 </EntandoCode>
 
 2. Create the namespace for the Entando Application
@@ -162,7 +162,7 @@ kubectl create namespace entando
 ```
 3. Download the `entando-operator-config` template so you can configure the [Entando Operator](../consume/entando-operator.md). 
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
 
 4. Edit the `entando-operator-config.yaml` to set `data/entando.requires.filesystem.group.override: "true"`
 ```yaml
@@ -178,7 +178,7 @@ kubectl apply -f entando-operator-config.yaml -n entando
 
 6. Apply the namespace-scoped custom resources
 
-<EntandoCode>kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
+<EntandoCode>kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
 
 7. You can use `kubectl get pods -n entando --watch` to see the initial pods start up. Use `Ctrl+C` to exit.
 ```
@@ -191,7 +191,7 @@ entando-operator-5b5465788b-ghb25      1/1     Running   0          5m53s
 ### Configure the Entando Application
 1. Download the `entando-app.yaml` template
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
 
 2. Edit `entando-app.yaml` and replace YOUR-HOST-NAME with the NGINX address from above. See the [Custom Resources overview](../../docs/reference/entandoapp-cr.md) for details on other `EntandoApp` options.
 ```yaml

vuepress/docs/next/tutorials/getting-started/gke-install.md

@@ -70,7 +70,7 @@ NGINX is working correctly if a `404 Not Found` NGINX error page is generated wh
 
 1. Download and apply the custom resource definitions (CRDs) to the cluster. This must be done once per cluster.
 
-<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
+<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
 </EntandoCode>
 
 2. Create a namespace for the Entando Application. If you choose a name other than "entando," update the following commands wherever a namespace is provided.
@@ -79,7 +79,7 @@ kubectl create namespace entando
 ```
 3. Download the `entando-operator-config` template to configure the [Entando Operator](../consume/entando-operator.md):
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-operator-config.yaml"</EntandoCode>
 
 4. Edit the `entando-operator-config.yaml` to add two properties:
 ```yaml
@@ -93,7 +93,7 @@ kubectl apply -f entando-operator-config.yaml -n entando
 ````
 6. Install the namespace-scoped resources:
 
-<EntandoCode>kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
+<EntandoCode>kubectl apply -n entando -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/namespace-resources.yaml</EntandoCode>
 
 7. Use `kubectl get pods -n entando --watch` to observe the base pods initialize. Exit this command via `Ctrl+C`.
 ```sh
@@ -106,7 +106,7 @@ entando-operator-5b5465788b-ghb25      1/1     Running   0          95s
 ### Configure the Entando Application
 1. Download the `entando-app.yaml` template:
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
 
 2. Edit `entando-app.yaml`. Replace `YOUR-HOST-NAME` with `EXTERNAL-IP` + `.nip.io`. See [the EntandoApp custom resource overview](../../docs/reference/entandoapp-cr.md) for additional options.
 ```yaml

vuepress/docs/next/tutorials/getting-started/openshift-install-by-operator.md

@@ -16,7 +16,7 @@ Scenario 1 is similar to the Entando quickstart style of deployment which can be
 ## Add the Entando Operator to the OperatorHub
 A cluster admin can add the current version of the Entando Operator into the local OperatorHub using the following command.
 
-<EntandoCode>oc apply -f https://raw.githubusercontent.com/entando/entando-releases/{{$site.themeConfig.entando.fixpack.v72}}/dist/ge-1-1-6/samples/openshift-catalog-source.yaml</EntandoCode>
+<EntandoCode>oc apply -f https://raw.githubusercontent.com/entando/entando-releases/{{$site.themeConfig.entando.fixpack.v73}}/dist/ge-1-1-6/samples/openshift-catalog-source.yaml</EntandoCode>
 
 ## Scenario 1 - Embedded Database
 The initial scenario deploys the operator and Entando Application into a single namespace. We start with the smallest application footprint by using an embedded database, although this is not recommended for production use cases.
@@ -28,7 +28,7 @@ The initial scenario deploys the operator and Entando Application into a single
 6. The install may take a few minutes to complete, after which you can click `View Operator` to see the operator in your namespace. You can also go to `Operators` → `Installed Operators` at any time and select it from there. 
 7. Now go to `EntandoApp` and click `Create EntandoApp`
    - Keep the default `my-app` as your application name or select your own
-   - Select the EntandoApp version: `7.2`
+   - Select the EntandoApp version: `7.3`
 8. Provide an `Ingress Host Name` specific to your namespace, e.g. `my-app.YOUR-BASE-OPENSHIFT-URL`. In CRC you can keep the default `entando.apps-crc.testing` for your first project.
 9. Change the `DBMS` value to `embedded`. This is the lightest and quickest way to test a full Entando Application. However, a non-embedded relational database is strongly recommended for production use.
 10. Click `Create`. The Entando Operator proceeds to deploy the appropriate resources. 
@@ -42,7 +42,7 @@ For this scenario we prepare a more production-like configuration. Here we switc
 Now create a new application, this time using PostgreSQL.
 1. Go to `EntandoApp` and click `Create instance`
    - Keep the default `my-app` as your application name or select your own
-   - Select the EntandoApp version: `7.2`
+   - Select the EntandoApp version: `7.3`
 2. Set the `Ingress Host Name` as in Scenario 1 above
 3. Keep the default `DBMS` value of `postgresql`  
 4. Click `Create`. The Entando Operator now deploys the appropriate resources as in Scenario 1 but with the addition of a PostgreSQL database deployment.
@@ -54,7 +54,7 @@ This scenario sets up PostgreSQL, like Scenario 2, but also enables SSL using Op
 
 1. Go to `EntandoApp` and click `Create instance`
    - Keep the default `my-app` as your application name or select your own
-   - Select the EntandoApp version: `7.2`
+   - Select the EntandoApp version: `7.3`
    - Set the `Ingress Host Name` as in Scenario 1 above
    - Keep the default `DBMS` value of `postgresql`
 2. Expand the `Advanced Configuration` section
@@ -117,7 +117,7 @@ Now let's create a new application similar to Scenario 3, but with the self-sign
 
 11. Go to `EntandoApp` and click `Create instance`
   - Keep the default `my-app` as your application name or select your own
-  - Select the EntandoApp version: `7.2`
+  - Select the EntandoApp version: `7.3`
   - Set the `Ingress Host Name` as in Scenario 1 above. It should match the CN used to generate the certificate in step 1.
   - Keep the default `DBMS` value as `postgresql`
 12. Click `Create`. The Entando Operator now proceeds to deploy the appropriate resources.

vuepress/docs/next/tutorials/getting-started/openshift-install.md

@@ -26,7 +26,7 @@ oc login --token=sha256~TO3QCeoLSbprlGZARBOBVAoaKFeb9Ag0RxztYifAcjE --server=htt
 
 2. Install the cluster-scoped custom resource definitions (CRDs). This step is only required once per cluster.
 
-<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
+<EntandoCode>kubectl apply -f https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/namespace-scoped-deployment/cluster-resources.yaml
 </EntandoCode>
 
 3. Create the project for your application
@@ -42,13 +42,13 @@ The remaining steps in this tutorial can be performed by a user with project-lev
 
 2. Install the namespace-scoped custom resources
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6//namespace-scoped-deployment/namespace-resources.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6//namespace-scoped-deployment/namespace-resources.yaml"</EntandoCode>
 
 
 ## Configure the Entando Application
 1. Download the `entando-app.yaml` template
 
-<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v72 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
+<EntandoCode>curl -sLO "https://raw.githubusercontent.com/entando/entando-releases/{{ $site.themeConfig.entando.fixpack.v73 }}/dist/ge-1-1-6/samples/entando-app.yaml"</EntandoCode>
 
 2. Determine the hostname for your application, YOUR-HOST-NAME
   - If you're deploying to a managed cluster: