Force image.tag version to workaround the helm chart tag version

lgrateau · lgrateau · commit 47acc1f159f6 · 2024-06-25T16:41:27.000+02:00
diff --git a/authentication/AzureAD/README_WITH_CLIENT_SECRET.md b/authentication/AzureAD/README_WITH_CLIENT_SECRET.md
@@ -316,7 +316,7 @@ You can now install the product. We will use the PostgreSQL internal database an
   See the [Preparing to install](https://www.ibm.com/docs/en/odm/9.0.0?topic=production-preparing-install-operational-decision-manager) documentation for additional information.
 
   ```shell
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
@@ -336,7 +336,7 @@ You can now install the product. We will use the PostgreSQL internal database an
   When the NGINX Ingress Controller is ready, you can install the ODM release with:
 
   ```
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
diff --git a/authentication/AzureAD/README_WITH_PRIVATE_KEY_JWT.md b/authentication/AzureAD/README_WITH_PRIVATE_KEY_JWT.md
@@ -247,7 +247,7 @@ You can now install the product. We will use the PostgreSQL internal database an
   See the [Preparing to install](https://www.ibm.com/docs/en/odm/9.0.0?topic=production-preparing-install-operational-decision-manager) documentation for additional information.
 
   ```shell
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
@@ -268,7 +268,7 @@ You can now install the product. We will use the PostgreSQL internal database an
   When the NGINX Ingress Controller is ready, you can install the ODM release with:
 
   ```
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
diff --git a/authentication/Cognito/README.md b/authentication/Cognito/README.md
@@ -516,7 +516,7 @@ In the **Container software library** tile, verify your entitlement on the **Vie
   See the [Preparing to install](https://www.ibm.com/docs/en/odm/9.0.0?topic=production-preparing-install-operational-decision-manager) documentation for more information.
 
   ```shell
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
@@ -536,7 +536,7 @@ In the **Container software library** tile, verify your entitlement on the **Vie
   When the NGINX Ingress Controller is ready, you can install the ODM release with:
 
   ```
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
diff --git a/authentication/Keycloak/README.md b/authentication/Keycloak/README.md
@@ -445,7 +445,7 @@ You can now install the product. We will use the PostgreSQL internal database an
   See the [Preparing to install](https://www.ibm.com/docs/en/odm/9.0.0?topic=production-preparing-install-operational-decision-manager) documentation for more information.
 
   ```shell
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
@@ -466,7 +466,7 @@ You can now install the product. We will use the PostgreSQL internal database an
   When the NGINX Ingress Controller is ready, you can install the ODM release with:
 
   ```shell
-  helm install my-odm-release ibm-helm/ibm-odm-prod \
+  helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set license=true \
diff --git a/authentication/Okta/README.md b/authentication/Okta/README.md
@@ -302,7 +302,7 @@ In this step, we augment the token with meta-information that is required by the
     You can now install the product. We will use the PostgreSQL internal database and disable the data persistence (`internalDatabase.persistence.enabled=false`) to avoid any platform complexity concerning persistent volume allocation.
 
     ```
-    helm install my-odm-release ibm-helm/ibm-odm-prod \
+    helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
           --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
           --set oidc.enabled=true \
           --set internalDatabase.persistence.enabled=false \
diff --git a/platform/azure/README-Azure-SQL-MI.md b/platform/azure/README-Azure-SQL-MI.md
@@ -52,7 +52,7 @@ kubectl create secret generic <odmdbsecret> --from-literal=db-user=<sqlmiadmin>
 Then you can deploy ODM with:
 
 ```bash
-helm install <release> ibmcharts/ibm-odm-prod --version 24.0.0 \
+helm install <release> ibmcharts/ibm-odm-prod \
         --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
         --set image.tag=${ODM_VERSION:-9.0.0.0} --set service.type=LoadBalancer \
         --set externalDatabase.type=sqlserver \
diff --git a/platform/azure/README.md b/platform/azure/README.md
@@ -308,7 +308,7 @@ az aks update --name <cluster> --resource-group <resourcegroup> --load-balancer-
 You can now install the product:
 
 ```shell
-helm install <release> ibmcharts/ibm-odm-prod --version 24.0.0 \
+helm install <release> ibmcharts/ibm-odm-prod  \
         --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
         --set image.tag=${ODM_VERSION:-9.0.0.0} --set service.type=LoadBalancer \
         --set externalDatabase.type=postgres \
@@ -396,7 +396,7 @@ You might want to access ODM components through a single external IP address.
 You can reuse the secret with TLS certificate created [above](#manage-adigital-certificate-10-min):
 
 ```shell
-helm install <release> ibmcharts/ibm-odm-prod --version 24.0.0 \
+helm install <release> ibmcharts/ibm-odm-prod \
         --set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
         --set image.tag=${ODM_VERSION:-9.0.0.0} \
         --set externalDatabase.type=postgres \
diff --git a/platform/eks/README-NGINX.md b/platform/eks/README-NGINX.md
@@ -37,7 +37,7 @@ To install ODM with the AWS RDS PostgreSQL database created in [step 2](README.m
   - `<RDS_DATABASE_NAME>`: the initial database name defined when creating the RDS database
 
 ```bash
-helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-nginx-values.yaml
+helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-rds-nginx-values.yaml
 ```
 
 > **Note**
@@ -49,7 +49,7 @@ helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-nginx-v
 > - Get the [eks-nginx-values.yaml](./eks-nginx-values.yaml) file:
 >
 > ```bash
-> helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-nginx-values.yaml
+> helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-nginx-values.yaml
 > ```
 
 ## Track ODM usage with the IBM License Service with NGINX Ingress Controller
diff --git a/platform/eks/README.md b/platform/eks/README.md
@@ -229,7 +229,7 @@ To install ODM with the AWS RDS PostgreSQL database created in [step 2](#2-creat
   - `<RDS_DATABASE_NAME>` is the initial database name defined when creating the RDS database
 
 ```bash
-helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-values.yaml
+helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-rds-values.yaml
 ```
 
 > **Note**
@@ -239,7 +239,7 @@ helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-values.
 >   - `<AWS-AccountId>` is your AWS Account Id
 >
 >```bash
->helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-values.yaml
+>helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-values.yaml
 >```
 
 > **Note**
diff --git a/platform/gcloud/README.md b/platform/gcloud/README.md
@@ -247,7 +247,7 @@ It automatically creates an HTTPS GKE load balancer. We will disable the ODM int
 - Install the chart from IBM's public Helm charts repository:
 
     ```
-    helm install <release> ibm-helm/ibm-odm-prod --version 23.2.0 -f gcp-values.yaml
+    helm install <release> ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f gcp-values.yaml
     ```
 
   > NOTE: You might prefer to access ODM components through the NGINX Ingress controller instead of using the IP addresses. If so, please follow [these instructions](README_NGINX.md).
diff --git a/platform/gcloud/README_NGINX.md b/platform/gcloud/README_NGINX.md
@@ -28,7 +28,7 @@ The secured HTTPS communication is managed by the NGINX ingress controller. So,
 Replace the placeholders in the [gcp-values.yaml](./gcp-values.yaml) file and install the chart:
 
 ```
-helm install mycompany ibm-helm/ibm-odm-prod --version 24.0.0 \
+helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
     -f gcp-values.yaml \
     --set service.ingress.annotations={"kubernetes.io/ingress.class: nginx"}
 ```
diff --git a/platform/minikube/README.md b/platform/minikube/README.md
@@ -103,7 +103,7 @@ ibmcharts/ibm-odm-prod            24.0.0        9.0.0.0     IBM Operational Deci
 Get the [minikube-values.yaml](./minikube-values.yaml) file and run the following command:
 
 ```shell
-helm install my-odm-release ibmcharts/ibm-odm-prod -f minikube-values.yaml
+helm install my-odm-release ibmcharts/ibm-odm-prod --set image.tag=9.0.0.0 -f minikube-values.yaml
 ```
 
 #### b. Check the topology
diff --git a/platform/roks/README.md b/platform/roks/README.md
@@ -97,7 +97,7 @@ ibm-helm/ibm-odm-prod   24.0.0        9.0.0.0     IBM Operational Decision Manag
 Get the [roks-values.yaml](./roks-values.yaml) file and install your ODM instance:
 
 ```bash
-helm install roks-tuto ibm-helm/ibm-odm-prod --version 24.0.0 -f roks-values.yaml
+helm install roks-tuto ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f roks-values.yaml
 ```
 
 > This configuration will deployed ODM with a sample database. You should used your own database such as [IBM Cloud Databases for PostgreSQL](https://www.ibm.com/products/databases-for-postgresql) for production.
@@ -166,7 +166,7 @@ oc create secret tls default-ingress-cert --cert=./tls.crt --key=./tls.key -n od
 - Get the [roks-sticky-values.yaml](./roks-sticky-values.yaml) file and launch your ODM instance :
 
 ```bash
-helm install roks-sticky-tuto ibm-helm/ibm-odm-prod --version 24.0.0 -f roks-sticky-values.yaml
+helm install roks-sticky-tuto ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f roks-sticky-values.yaml
 ```
 
 The ODM containers will embed the ROKS domain certificates. Additionally, two Decision Center pods will be launched to verify the sticky session behavior.
