Skip to content

Commit 47acc1f

Browse files
lgrateaulgrateau
committed
Force image.tag version to workaround the helm chart tag version
1 parent 6d31168 commit 47acc1f

File tree

13 files changed

+21
-21
lines changed

13 files changed

+21
-21
lines changed

‎authentication/AzureAD/README_WITH_CLIENT_SECRET.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -316,7 +316,7 @@ You can now install the product. We will use the PostgreSQL internal database an
316316
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.
317317
318318
```shell
319-
helm install my-odm-release ibm-helm/ibm-odm-prod \
319+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
320320
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
321321
--set oidc.enabled=true \
322322
--set license=true \
@@ -336,7 +336,7 @@ You can now install the product. We will use the PostgreSQL internal database an
336336
When the NGINX Ingress Controller is ready, you can install the ODM release with:
337337
338338
```
339-
helm install my-odm-release ibm-helm/ibm-odm-prod \
339+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
340340
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
341341
--set oidc.enabled=true \
342342
--set license=true \

‎authentication/AzureAD/README_WITH_PRIVATE_KEY_JWT.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ You can now install the product. We will use the PostgreSQL internal database an
247247
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.
248248
249249
```shell
250-
helm install my-odm-release ibm-helm/ibm-odm-prod \
250+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
251251
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
252252
--set oidc.enabled=true \
253253
--set license=true \
@@ -268,7 +268,7 @@ You can now install the product. We will use the PostgreSQL internal database an
268268
When the NGINX Ingress Controller is ready, you can install the ODM release with:
269269
270270
```
271-
helm install my-odm-release ibm-helm/ibm-odm-prod \
271+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
272272
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
273273
--set oidc.enabled=true \
274274
--set license=true \

‎authentication/Cognito/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -516,7 +516,7 @@ In the **Container software library** tile, verify your entitlement on the **Vie
516516
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.
517517

518518
```shell
519-
helm install my-odm-release ibm-helm/ibm-odm-prod \
519+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
520520
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
521521
--set oidc.enabled=true \
522522
--set license=true \
@@ -536,7 +536,7 @@ In the **Container software library** tile, verify your entitlement on the **Vie
536536
When the NGINX Ingress Controller is ready, you can install the ODM release with:
537537

538538
```
539-
helm install my-odm-release ibm-helm/ibm-odm-prod \
539+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
540540
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
541541
--set oidc.enabled=true \
542542
--set license=true \

‎authentication/Keycloak/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -445,7 +445,7 @@ You can now install the product. We will use the PostgreSQL internal database an
445445
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.
446446

447447
```shell
448-
helm install my-odm-release ibm-helm/ibm-odm-prod \
448+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
449449
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
450450
--set oidc.enabled=true \
451451
--set license=true \
@@ -466,7 +466,7 @@ You can now install the product. We will use the PostgreSQL internal database an
466466
When the NGINX Ingress Controller is ready, you can install the ODM release with:
467467

468468
```shell
469-
helm install my-odm-release ibm-helm/ibm-odm-prod \
469+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
470470
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
471471
--set oidc.enabled=true \
472472
--set license=true \

‎authentication/Okta/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -302,7 +302,7 @@ In this step, we augment the token with meta-information that is required by the
302302
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.
303303
304304
```
305-
helm install my-odm-release ibm-helm/ibm-odm-prod \
305+
helm install my-odm-release ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
306306
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=icregistry-secret \
307307
--set oidc.enabled=true \
308308
--set internalDatabase.persistence.enabled=false \

‎platform/azure/README-Azure-SQL-MI.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ kubectl create secret generic <odmdbsecret> --from-literal=db-user=<sqlmiadmin>
5252
Then you can deploy ODM with:
5353

5454
```bash
55-
helm install <release> ibmcharts/ibm-odm-prod --version 24.0.0 \
55+
helm install <release> ibmcharts/ibm-odm-prod \
5656
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
5757
--set image.tag=${ODM_VERSION:-9.0.0.0} --set service.type=LoadBalancer \
5858
--set externalDatabase.type=sqlserver \

‎platform/azure/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -308,7 +308,7 @@ az aks update --name <cluster> --resource-group <resourcegroup> --load-balancer-
308308
You can now install the product:
309309

310310
```shell
311-
helm install <release> ibmcharts/ibm-odm-prod --version 24.0.0 \
311+
helm install <release> ibmcharts/ibm-odm-prod \
312312
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
313313
--set image.tag=${ODM_VERSION:-9.0.0.0} --set service.type=LoadBalancer \
314314
--set externalDatabase.type=postgres \
@@ -396,7 +396,7 @@ You might want to access ODM components through a single external IP address.
396396
You can reuse the secret with TLS certificate created [above](#manage-adigital-certificate-10-min):
397397

398398
```shell
399-
helm install <release> ibmcharts/ibm-odm-prod --version 24.0.0 \
399+
helm install <release> ibmcharts/ibm-odm-prod \
400400
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
401401
--set image.tag=${ODM_VERSION:-9.0.0.0} \
402402
--set externalDatabase.type=postgres \

‎platform/eks/README-NGINX.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To install ODM with the AWS RDS PostgreSQL database created in [step 2](README.m
3737
- `<RDS_DATABASE_NAME>`: the initial database name defined when creating the RDS database
3838

3939
```bash
40-
helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-nginx-values.yaml
40+
helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-rds-nginx-values.yaml
4141
```
4242

4343
> **Note**
@@ -49,7 +49,7 @@ helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-nginx-v
4949
> - Get the [eks-nginx-values.yaml](./eks-nginx-values.yaml) file:
5050
>
5151
> ```bash
52-
> helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-nginx-values.yaml
52+
> helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-nginx-values.yaml
5353
> ```
5454
5555
## Track ODM usage with the IBM License Service with NGINX Ingress Controller

‎platform/eks/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ To install ODM with the AWS RDS PostgreSQL database created in [step 2](#2-creat
229229
- `<RDS_DATABASE_NAME>` is the initial database name defined when creating the RDS database
230230

231231
```bash
232-
helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-values.yaml
232+
helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-rds-values.yaml
233233
```
234234

235235
> **Note**
@@ -239,7 +239,7 @@ helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-rds-values.
239239
> - `<AWS-AccountId>` is your AWS Account Id
240240
>
241241
>```bash
242-
>helm install mycompany ibm-helm/ibm-odm-prod --version 23.2.0 -f eks-values.yaml
242+
>helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f eks-values.yaml
243243
>```
244244
245245
> **Note**

‎platform/gcloud/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ It automatically creates an HTTPS GKE load balancer. We will disable the ODM int
247247
- Install the chart from IBM's public Helm charts repository:
248248

249249
```
250-
helm install <release> ibm-helm/ibm-odm-prod --version 23.2.0 -f gcp-values.yaml
250+
helm install <release> ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f gcp-values.yaml
251251
```
252252
253253
> 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).

‎platform/gcloud/README_NGINX.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The secured HTTPS communication is managed by the NGINX ingress controller. So,
2828
Replace the placeholders in the [gcp-values.yaml](./gcp-values.yaml) file and install the chart:
2929

3030
```
31-
helm install mycompany ibm-helm/ibm-odm-prod --version 24.0.0 \
31+
helm install mycompany ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 \
3232
-f gcp-values.yaml \
3333
--set service.ingress.annotations={"kubernetes.io/ingress.class: nginx"}
3434
```

‎platform/minikube/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ ibmcharts/ibm-odm-prod 24.0.0 9.0.0.0 IBM Operational Deci
103103
Get the [minikube-values.yaml](./minikube-values.yaml) file and run the following command:
104104

105105
```shell
106-
helm install my-odm-release ibmcharts/ibm-odm-prod -f minikube-values.yaml
106+
helm install my-odm-release ibmcharts/ibm-odm-prod --set image.tag=9.0.0.0 -f minikube-values.yaml
107107
```
108108

109109
#### b. Check the topology

‎platform/roks/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ ibm-helm/ibm-odm-prod 24.0.0 9.0.0.0 IBM Operational Decision Manag
9797
Get the [roks-values.yaml](./roks-values.yaml) file and install your ODM instance:
9898

9999
```bash
100-
helm install roks-tuto ibm-helm/ibm-odm-prod --version 24.0.0 -f roks-values.yaml
100+
helm install roks-tuto ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f roks-values.yaml
101101
```
102102

103103
> 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
166166
- Get the [roks-sticky-values.yaml](./roks-sticky-values.yaml) file and launch your ODM instance :
167167

168168
```bash
169-
helm install roks-sticky-tuto ibm-helm/ibm-odm-prod --version 24.0.0 -f roks-sticky-values.yaml
169+
helm install roks-sticky-tuto ibm-helm/ibm-odm-prod --set image.tag=9.0.0.0 -f roks-sticky-values.yaml
170170
```
171171

172172
The ODM containers will embed the ROKS domain certificates. Additionally, two Decision Center pods will be launched to verify the sticky session behavior.

0 commit comments

Comments
 (0)