Update odm appversion to 9.0.0.1 & chart version to 24.1.0

Author: siasin

authentication/Cognito/README.md

@@ -505,7 +505,7 @@ In the **Container software library** tile, verify your entitlement on the **Vie
   ```shell
   helm search repo ibm-odm-prod
   NAME                          CHART VERSION   APP VERSION     DESCRIPTION
-  ibm-helm/ibm-odm-prod         24.0.0          9.0.0.0        IBM Operational Decision Manager
+  ibm-helm/ibm-odm-prod         24.1.0          9.0.0.1        IBM Operational Decision Manager
   ```
 
 ### 3. Run the `helm install` command

contrib/monitor/mpmetrics/README.md

@@ -70,7 +70,7 @@ Create the monitor-secret
   ```shell
   helm search repo ibm-odm-prod
   NAME                  	CHART VERSION	APP VERSION	DESCRIPTION
-  ibm-helm/ibm-odm-prod	        24.0.0       	9.0.0.0   	IBM Operational Decision Manager
+  ibm-helm/ibm-odm-prod	  24.1.0       	9.0.0.1   	IBM Operational Decision Manager
   ```
 
 ### 3. Run the `helm install` command

contrib/monitor/opentelemetry/README.md

@@ -90,7 +90,7 @@ helm repo update
 ```bash
 $ helm search repo ibm-odm-prod
 NAME                             	CHART VERSION	APP VERSION	DESCRIPTION
-ibm-helm/ibm-odm-prod           	24.0.0       	9.0.0.0   	IBM Operational Decision Manager
+ibm-helm/ibm-odm-prod           	24.1.0       	9.0.0.1   	IBM Operational Decision Manager
 ```
 
 ### Install an IBM Operational Decision Manager release (10 min)

contrib/secrets-store/README.md

@@ -60,7 +60,7 @@ HashiCorp Vault must be up and running. An [on-prem installation description](RE
 - [Secrets Store CSI Driver](https://secrets-store-csi-driver.sigs.k8s.io/) already installed.
 - [HashiCorp Vault provider driver](https://developer.hashicorp.com/vault/tutorials/kubernetes/kubernetes-secret-store-driver) already installed
 - [Helm](https://helm.sh/docs/intro/install/)
-- Access to Operational Decision Manager on Container 9.0.0.0 images
+- Access to Operational Decision Manager on Container 9.0.0.1 images
 
 > Note: The first and second steps are described in the [companion document](README-External_Vault.md) when you use OCP.
 
@@ -160,7 +160,7 @@ Check that you can access ODM charts:
 ```bash
 helm search repo ibm-odm-prod
 NAME                  	CHART VERSION   APP VERSION     DESCRIPTION
-ibm-helm/ibm-odm-prod   24.0.0       	  9.0.0.0         IBM Operational Decision Manager
+ibm-helm/ibm-odm-prod   24.1.0       	  9.0.0.1         IBM Operational Decision Manager
 ```
 
 #### Data to be injected in the pods

contrib/secrets-store/values-default-vault.yaml

@@ -3,7 +3,7 @@ license: true
 
 image:
   repository: cp.stg.icr.io/cp/cp4a/odm/
-  tag: 9.0.0.0
+  tag: 9.0.0.1
 ## Optionally specify an list of imagePullSecrets.
 ## Secrets must be manually created in the namespace.
 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

contrib/vault-initcontainer/README.md

@@ -58,7 +58,7 @@ The diagram visually represents the secure flow of secrets data from the central
    * [Vault client](https://developer.hashicorp.com/vault/install)
    * [Helm v3](https://helm.sh/docs/intro/install/)
    * [Kustomize](https://github.com/kubernetes-sigs/kustomize/releases)
-   * Operational Decision Manager on Container 9.0.0.0
+   * Operational Decision Manager on Container 9.0.0.1
 
 > Note: This documentation has been tested with a HashiCorp evaluation instance. We assume that the procedure will remain the same for the commercial product.
 

contrib/vault-initcontainer/openid/values-default-vault.yaml

@@ -11,7 +11,7 @@ usersPassword: "odmAdmin"
 
 image:
   repository: "cp.stg.icr.io/cp/cp4a/odm/"
-  tag: 9.0.0.0
+  tag: 9.0.0.1
   pullPolicy: IfNotPresent
 ## Optionally specify an list of imagePullSecrets.
 ## Secrets must be manually created in the namespace.

contrib/vault-initcontainer/values-default-vault.yaml

@@ -11,7 +11,7 @@ usersPassword: "odmAdmin"
 
 image:
   repository: "cp.stg.icr.io/cp/cp4a/odm/"
-  tag: 9.0.0.0
+  tag: 9.0.0.1
   pullPolicy: IfNotPresent
 ## Optionally specify an list of imagePullSecrets.
 ## Secrets must be manually created in the namespace.