Skip to content

Commit d13b66e

Browse files
authored
simplify k8s
1 parent 93b5b2a commit d13b66e

File tree

1 file changed

+40
-17
lines changed

1 file changed

+40
-17
lines changed

decisioncenter/businessvalueeditor/README-KUBERNETES.md

Lines changed: 40 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -7,38 +7,59 @@ Before following the steps below, make sure you have built the images as explain
77

88
## 1. Uploading ZIP file on a file server
99

10-
The customization ZIP file can be made available to Decision Center in two ways:
11-
1. the **legacy way**: by copying the JARs to a PVC and referencing this PVC using the parameter `decisionCenter.customlibPvc`
12-
1. or the **new way** (since 9.0 only): by copying the JARs on a file server and referencing the files to download from this file server using the parameter `decisionCenter.downloadUrl`
10+
Any file server reachable by Decision Center is suitable.
1311

14-
This document explains how to follow the **new way**. Any file server reachable by Decision Center is suitable. You can either use an existing one or follow the instructions [here](https://github.com/DecisionsDev/odm-docker-kubernetes/blob/vnext-release/contrib/file-server/README.md#setup-an-httpd-file-server) to deploy a httpd file server in a new pod.
12+
You can either use an existing one or follow the instructions [here](https://github.com/DecisionsDev/odm-docker-kubernetes/blob/vnext-release/contrib/file-server/README.md#setup-an-httpd-file-server) to deploy a httpd file server in a new pod.
1513

16-
However you must use the **legacy way** if you deploy a version of ODM older than 9.0. Here are some [instructions](https://www.ibm.com/docs/en/odm/9.0.0?topic=kubernetes-customizing-decision-center-business-console) in the documentation.
17-
18-
Upload the businessvalueeditor-1.0.zip file on the file server :
14+
Upload the **businessvalueeditor-1.0.zip** file on the file server :
1915
```
2016
curl -T businessvalueeditor/businessvalueeditor-source/target/businessvalueeditor-1.0.zip $FILESERVER_URL
2117
```
2218

2319
## 2. Deploying ODM
2420

25-
Add the public IBM Helm charts repository:
21+
To get access to the ODM material, you must have an IBM entitlement key to pull the images from the IBM Cloud Container registry.
2622

27-
```
28-
helm repo add ibmcharts https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm
29-
helm repo update
30-
````
23+
This is what will be used in the next step of this tutorial.
3124

32-
Check that you can access the ODM charts:
25+
#### a. Retrieve your entitled registry key
3326

27+
- Log in to [MyIBM Container Software Library](https://myibm.ibm.com/products-services/containerlibrary) with the IBMid and password that are associated with the entitled software.
28+
29+
- In the **Container Software and Entitlement Keys** tile, verify your entitlement on the **View library page**, and then go to *Entitlement keys* to retrieve the key.
30+
31+
#### b. Create a pull secret by running the kubectl create secret command
32+
33+
```bash
34+
oc create secret docker-registry my-odm-docker-registry --docker-server=cp.icr.io \
35+
--docker-username=cp --docker-password="<ENTITLEMENT_KEY>" --docker-email=<USER_EMAIL>
3436
```
35-
helm search repo ibm-odm-prod
36-
```
3737

38+
Where:
39+
40+
- `<ENTITLEMENT_KEY>`: The entitlement key from the previous step. Make sure to enclose the key in double quotes.
41+
- `<USER_EMAIL>`: The email address associated with your IBMid.
42+
43+
> **Note**
44+
> The `cp.icr.io` value for the docker-server parameter is the only registry domain name that contains the images. You must set the docker-username to `cp` to use the entitlement key as the docker-password.
45+
46+
The my-odm-docker-registry secret name is already used for the `image.pullSecrets` parameter when you run a Helm install of your containers. The `image.repository` parameter is also set by default to `cp.icr.io/cp/cp4a/odm`.
47+
48+
#### c. Add the public IBM Helm charts repository
49+
50+
```bash
51+
helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm
52+
helm repo update
3853
```
39-
NAME CHART VERSION APP VERSION DESCRIPTION
40-
ibmcharts/ibm-odm-prod <version> <version> IBM Operational Decision Manager License By in...
54+
55+
#### d. Check your access to the ODM chart
56+
57+
```bash
58+
$ helm search repo ibm-odm-prod
59+
NAME CHART VERSION APP VERSION DESCRIPTION
60+
ibm-helm/ibm-odm-prod 24.0.0 9.0.0.0 IBM Operational Decision Manager
4161
```
62+
#### e. Install an IBM Operational Decision Manager release
4263

4364
Create a file named **values.yaml**. This file will be used by the **helm install** command to specify the configuration parameters.
4465

@@ -51,6 +72,8 @@ decisionCenter:
5172

5273
Add all the other parameters suitable to your platform in `values.yaml`. Check this [link](https://github.com/DecisionsDev/odm-docker-kubernetes/tree/master/platform) for help.
5374

75+
If you are on OCP, you can use this [values.yaml](./businessvalueeditor-source/values.yaml) file by replacing `<FILESERVER_URL>` by the actual URL of the file server hosting the JARs.
76+
5477
```bash
5578
helm install businessvalueeditor-sample ibmcharts/ibm-odm-prod -f values.yaml
5679
```

0 commit comments

Comments
 (0)