Skip to content

Commit 37de20e

Browse files
PYLochouPYLochou
committed
New version + simplification (esp. location no more needed)
1 parent c48c5c7 commit 37de20e

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

‎platform/azure/README.md

+16-16
Original file line numberDiff line numberDiff line change
@@ -103,8 +103,7 @@ Use the `az aks create` command to create an AKS cluster. The following example
103103
104104
```shell
105105
az aks create --name <cluster> --resource-group <resourcegroup> --node-count 2 \
106-
--enable-cluster-autoscaler --min-count 2 --max-count 4 \
107-
--enable-addons monitoring --generate-ssh-keys [--location <azurelocation>]
106+
--enable-cluster-autoscaler --min-count 2 --max-count 4
108107
```
109108

110109
After a few minutes, the command completes and returns JSON-formatted information about the cluster. Make a note of the newly-created Resource Group that is displayed in the JSON output (e.g. "nodeResourceGroup": "<noderesourcegroup>") if you have to tag it, for example:
@@ -158,7 +157,7 @@ To get a good bandwidth between ODM containers and the database, choose the same
158157
```shell
159158
az postgres server create --name <postgresqlserver> --resource-group <resourcegroup> \
160159
--admin-user myadmin --admin-password 'passw0rd!' \
161-
--sku-name GP_Gen5_2 --version 11 [--location <azurelocation>]
160+
--sku-name GP_Gen5_2 --version 11
162161
```
163162

164163
> Note: The PostgreSQL server name must be unique within Azure.
@@ -219,7 +218,7 @@ To make sure your database and your AKS cluster can communicate, put in place fi
219218

220219
```shell
221220
az postgres server firewall-rule create --resource-group <resourcegroup> --server-name <postgresqlserver> \
222-
--name <rulename> --start-ip-address 0.0.0.0 --end-ip-address 255.255.255.255
221+
--name <rule> --start-ip-address 0.0.0.0 --end-ip-address 255.255.255.255
223222
```
224223

225224
## Prepare your environment for the ODM installation
@@ -263,7 +262,7 @@ Check that you can access the ODM charts:
263262
```shell
264263
helm search repo ibm-odm-prod
265264
NAME CHART VERSION APP VERSION DESCRIPTION
266-
ibmcharts/ibm-odm-prod 23.1.0 8.12.0.0 IBM Operational Decision Manager License By in...
265+
ibmcharts/ibm-odm-prod 23.2.0 8.12.0.1 IBM Operational Decision Manager License By in...
267266
```
268267

269268
### Create the database credentials secret for Azure PostgreSQL
@@ -312,7 +311,7 @@ You can now install the product:
312311
```shell
313312
helm install <release> ibmcharts/ibm-odm-prod --version 23.1.0 \
314313
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
315-
--set image.arch=amd64 --set image.tag=${ODM_VERSION:-8.12.0.0} --set service.type=LoadBalancer \
314+
--set image.arch=amd64 --set image.tag=${ODM_VERSION:-8.12.0.1} --set service.type=LoadBalancer \
316315
--set externalDatabase.type=postgres \
317316
--set externalDatabase.serverName=<postgresqlserver>.postgres.database.azure.com \
318317
--set externalDatabase.databaseName=postgres \
@@ -344,34 +343,35 @@ NAME READY STATUS RESTART
344343
By setting `service.type=LoadBalancer`, the services are exposed with public IPs to be accessed with the following command:
345344

346345
```shell
347-
kubectl get services
346+
kubectl get services --selector release=<release>
348347
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
349-
kubernetes ClusterIP 10.0.0.1 <none> 443/TCP 26h
350348
<release>-odm-decisioncenter LoadBalancer 10.0.141.125 xxx.xxx.xxx.xxx 9453:31130/TCP 22m
351349
<release>-odm-decisionrunner LoadBalancer 10.0.157.225 xxx.xxx.xxx.xxx 9443:31325/TCP 22m
352350
<release>-odm-decisionserverconsole LoadBalancer 10.0.215.192 xxx.xxx.xxx.xxx 9443:32448/TCP 22m
353351
<release>-odm-decisionserverconsole-notif ClusterIP 10.0.201.87 <none> 1883/TCP 22m
354352
<release>-odm-decisionserverruntime LoadBalancer 10.0.177.153 xxx.xxx.xxx.xxx 9443:31921/TCP 22m
355353
```
354+
356355
<!-- markdown-link-check-disable -->
357356
You can then open a browser on https://xxx.xxx.xxx.xxx:9453 to access Decision Center, and on https://xxx.xxx.xxx.xxx:9443 to access Decision Server console, Decision Server Runtime, and Decision Runner.
358357
<!-- markdown-link-check-enable -->
358+
359359
## Create an NGINX Ingress controller
360360

361361
Installing an NGINX Ingress controller allows you to access ODM components through a single external IP address instead of the different IP addresses as seen above. It is also mandatory to retrieve license usage through the IBM License Service.
362362

363363
1. Use the official YAML manifest:
364364

365365
```shell
366-
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.0/deploy/static/provider/cloud/deploy.yaml
366+
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/cloud/deploy.yaml
367367
```
368368

369369
> Note: The version will probably change after the publication of our documentation so please refer to the actual [documentation](https://kubernetes.github.io/ingress-nginx/deploy/#azure)!
370370

371371
2. Get the Ingress controller external IP address (it will appear 80 seconds or so after the resource application above):
372372

373373
```shell
374-
kubectl get service -l app.kubernetes.io/name=ingress-nginx -n ingress-nginx
374+
kubectl get service --selector app.kubernetes.io/name=ingress-nginx --namespace ingress-nginx
375375
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
376376
ingress-nginx-controller LoadBalancer 10.0.78.246 20.19.105.130 80:32208/TCP,443:30249/TCP 2m12s
377377
ingress-nginx-controller-admission ClusterIP 10.0.229.164 <none> 443/TCP 2m12s
@@ -396,9 +396,9 @@ 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 23.1.0 \
399+
helm install <release> ibmcharts/ibm-odm-prod --version 23.2.0 \
400400
--set image.repository=cp.icr.io/cp/cp4a/odm --set image.pullSecrets=<registrysecret> \
401-
--set image.arch=amd64 --set image.tag=${ODM_VERSION:-8.12.0.0} \
401+
--set image.arch=amd64 --set image.tag=${ODM_VERSION:-8.12.0.1} \
402402
--set externalDatabase.type=postgres \
403403
--set externalDatabase.serverName=<postgresqlserver>.postgres.database.azure.com \
404404
--set externalDatabase.databaseName=postgres \
@@ -426,7 +426,7 @@ helm install <release> ibmcharts/ibm-odm-prod --version 23.1.0 \
426426
Check that ODM services are in NodePort type:
427427

428428
```shell
429-
kubectl get services -l app.kubernetes.io/name=ibm-odm-prod
429+
kubectl get services --selector release=<release>
430430
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
431431
release-odm-decisioncenter NodePort 10.0.178.43 <none> 9453:32720/TCP 16m
432432
release-odm-decisionrunner NodePort 10.0.171.46 <none> 9443:30223/TCP 16m
@@ -471,14 +471,14 @@ kubectl create -f licensing-instance.yml
471471
After a couple of minutes, the NGINX load balancer reflects the Ingress configuration and you will be able to access the IBM License Service by retrieving the URL with this command:
472472

473473
```shell
474-
export LICENSING_URL=$(kubectl get ingress ibm-licensing-service-instance -n ibm-common-services |awk '{print $4}' |tail -1)/ibm-licensing-service-instance
475-
export TOKEN=$(oc get secret ibm-licensing-token -o jsonpath={.data.token} -n ibm-common-services |base64 -d)
474+
export LICENSING_URL=$(kubectl get ingress ibm-licensing-service-instance --namespace ibm-common-services --no-headers | awk '{print $4}')/ibm-licensing-service-instance
475+
export TOKEN=$(kubectl get secret ibm-licensing-token --output jsonpath={.data.token} --namespace ibm-common-services | base64 -d)
476476
```
477477

478478
You can access the `http://${LICENSING_URL}/status?token=${TOKEN}` URL to view the licensing usage, or retrieve the licensing report .zip file by running:
479479

480480
```shell
481-
curl -v "http://${LICENSING_URL}/snapshot?token=${TOKEN}" --output report.zip
481+
curl "http://${LICENSING_URL}/snapshot?token=${TOKEN}" --output report.zip
482482
```
483483

484484
If your IBM License Service instance is not running properly, refer to this [troubleshooting page](https://www.ibm.com/docs/en/cpfs?topic=software-troubleshooting).

0 commit comments

Comments
 (0)