You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: authentication/AzureAD/README_WITH_CLIENT_SECRET.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -359,7 +359,7 @@ You can now install the product. We will use the PostgreSQL internal database an
359
359
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.
Copy file name to clipboardExpand all lines: authentication/AzureAD/README_WITH_PRIVATE_KEY_JWT.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -254,7 +254,7 @@ You can now install the product. We will use the PostgreSQL internal database an
254
254
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.
Copy file name to clipboardExpand all lines: authentication/Cognito/README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -516,7 +516,7 @@ In the **Container software library** tile, verify your entitlement on the **Vie
516
516
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.
Copy file name to clipboardExpand all lines: authentication/Okta/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -329,7 +329,7 @@ In this step, we augment the token with meta-information that is required by the
329
329
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.
Copy file name to clipboardExpand all lines: platform/eks/README-ECR.md
+21-34Lines changed: 21 additions & 34 deletions
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ The related instructions in the online documentation are:
11
11
## Prerequisites:
12
12
13
13
- Install the following tools on your bastion host (if needed, refer to [Setting up a host to mirror images to a private registry](https://www.ibm.com/docs/en/odm/9.0.0?topic=installation-setting-up-host-mirror-images-private-registry)):
@@ -21,6 +22,12 @@ The related instructions in the online documentation are:
21
22
- github.com for CASE files and tools
22
23
- Amazon ECR
23
24
25
+
- Configure the `aws` CLI environment by running the following command:
26
+
```bash
27
+
aws configure
28
+
```
29
+
You will be prompted to provide your AWS Access Key ID, AWS Secret Access Key and the Default region name.
30
+
24
31
- Export the following environment variables (replace the placeholders `<AWS-Region>`, `<AWS-AccountId>`, `<ODM-CaseVersion>` and `<amd64|ppc64le|s390x>` with actual values):
25
32
26
33
```bash
@@ -65,34 +72,11 @@ The related instructions in the online documentation are:
65
72
66
73
This command generates the files `images-mapping.txt` and `image-content-source-policy.yaml` at `~/.ibm-pak/data/mirror/${CASE_NAME}/${CASE_VERSION}`. The `~/.ibm-pak/mirror` directory is also created.
67
74
68
-
- For CASE versions up to 1.7.x (included), append `-<architecture>` at the end of each line in`~/.ibm-pak/data/mirror/${CASE_NAME}/${CASE_VERSION}/images-mapping.txt` (where `<architecture>` can be `amd64`, `ppc64le`, or `s390x`).
69
-
70
-
- either manually,
71
-
- or by running the command below (on Linux only, not for MacOS):
72
-
73
-
```bash
74
-
sed -i "s/$/-${ARCHITECTURE}/"~/.ibm-pak/data/mirror/${CASE_NAME}/${CASE_VERSION}/images-mapping.txt
75
-
```
76
-
77
-
Here is an example of such a file after this modification:
For some interim fixes, the file `images-mapping.txt` need to be modified differently. The instructions can be found in the readme page of the interim fix.
89
-
90
-
91
75
- Store authentication credentials of the source Docker registry `cp.icr.io` and the target Amazon ECR.
92
76
93
77
> NOTE:
94
78
You must specify the user as `cp` to log in to `cp.icr.io`. The password is your Entitlement key from the [IBM Cloud Container Registry](https://myibm.ibm.com/products-services/containerlibrary).
95
-
79
+
96
80
- If you use Podman:
97
81
98
82
> Note: by default Podman reads and stores credentials in`${XDG_RUNTIME_DIR}/containers/auth.json`. Read more [here](https://docs.podman.io/en/stable/markdown/podman-login.1.html).
@@ -170,9 +154,9 @@ The related instructions in the online documentation are:
170
154
171
155
- Find the Helm Chart version related to your CASE version:
172
156
173
-
For instance, if you choose the CASE version `1.8.0`, then the Helm chart version should be `24.0.0` and you should set:
157
+
For instance, if you choose the CASE version `1.9.0`, then the Helm chart version should be `24.1.0` and you should set:
174
158
```bash
175
-
export CHART_VERSION=24.0.0
159
+
export CHART_VERSION=24.1.0
176
160
```
177
161
178
162
You can find the Helm chart version related to a given CASE version:
@@ -181,27 +165,30 @@ The related instructions in the online documentation are:
181
165
182
166
- For an interim fix: click the link foryour version of ODMin the page [Operational Decision Manager Interim Fixes](https://www.ibm.com/support/pages/operational-decision-manager-interim-fixes) and then check the table "Interim fix for ODM on Certified Kubernetes".
183
167
184
-
- Alternatively, you can also run the command`tree ~/.ibm-pak/data/cases/ibm-odm-prod/` (on the bastion host), and you can find the chart version number in the name of the file `ibm-odm-prod-<CHART_VERSION>.tgz` located in`<CASE_VERSION>/charts/`:
168
+
- Alternatively, you can also run the command`tree ~/.ibm-pak/data/cases/ibm-odm-prod/` (on the bastion host), and you can find the chart version number corresponding to the file `ibm-odm-prod-<CHART_VERSION>.tgz`. Below is an example for CASE version `1.9.0` that corresponds to Helm chart version `24.1.0`:
185
169
186
170
```bash
187
171
/home/user/.ibm-pak/data/cases/ibm-odm-prod/
188
-
└── 1.8.0
172
+
└── 1.9.0
189
173
├── caseDependencyMapping.csv
190
174
├── charts
191
-
│ └── ibm-odm-prod-24.0.0.tgz
175
+
│ └── ibm-odm-prod-24.1.0.tgz
192
176
├── component-set-config.yaml
193
-
├── ibm-odm-prod-1.8.0-airgap-metadata.yaml
194
-
├── ibm-odm-prod-1.8.0-charts.csv
195
-
├── ibm-odm-prod-1.8.0-images.csv
196
-
├── ibm-odm-prod-1.8.0.tgz
177
+
├── ibm-odm-prod-1.9.0-airgap-metadata.yaml
178
+
├── ibm-odm-prod-1.9.0-charts.csv
179
+
├── ibm-odm-prod-1.9.0-images.csv
180
+
├── ibm-odm-prod-1.9.0.tgz
197
181
└── resourceIndexes
198
182
└── ibm-odm-prod-resourcesIndex.yaml
199
183
```
200
-
- Run the `helm install`command below:
184
+
- Run the `helm install`command below to install ODM:
> By using `eks-values.yaml`, ODM with a PostgreSQL internal database will be installed. It requires an ALB ingress controller and a server certificate. For more information, see [Provision an AWS Load Balancer Controller](README.md#d-provision-an-aws-load-balancer-controller) and [Manage a digital certificate](README.md#4-manage-a-digital-certificate-10-min).
> 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).
0 commit comments