Skip to content

Latest commit

 

History

History
75 lines (52 loc) · 3.51 KB

README.md

File metadata and controls

75 lines (52 loc) · 3.51 KB

Install Operational Decision Manager with the Kubernetes CLI

Refer to the top repository readme to find instructions on how to push and tag the product container images to your Docker registry.

  1. If Helm is not installed in your Kubernetes cluster, install Helm 2.9.1.

  2. Download the ibm-odm-prod-2.1.0.tgz Helm chart.

  3. Create a chart YAML template file with the default configuration parameters by using the following command. The --name argument sets the name of the release to install.

    $ helm template \
  --name my-odm-prod-release \
  /path/to/ibm-odm-prod-2.1.0.tgz > generated-k8s-templates.yaml

  4. Install my-odm-prod-release with the default configuration by using the following command.

    $ kubectl apply -f generated-k8s-templates.yaml

    The package is deployed asynchronously in a matter of minutes, and is composed of several services.

    Note: You can check the status of the pods that you created:

    $ kubectl get pods
NAME                                                READY   STATUS    RESTARTS   AGE
my-odm-prod-release-dbserver-***                    1/1     Running   0          44m
my-odm-prod-release-odm-decisioncenter-***          1/1     Running   0          44m
my-odm-prod-release-odm-decisionrunner-***          1/1     Running   0          44m
my-odm-prod-release-odm-decisionserverconsole-***   1/1     Running   0          44m
my-odm-prod-release-odm-decisionserverruntime-***   1/1     Running   0          44m

    The release is an instance of the ibm-odm-prod chart. All of the Operational Decision Manager components are now running in a Kubernetes cluster.

    To verify a deployment, go back to the Post installation steps.

Customize a Kubernetes release of Operational Decision Manager

Refer to the ODM for production Certified Kubernetes parameters for a complete list of values that you can configure.

To customize the install with --set key=value arguments

Using Helm, you can specify each parameter with a --set key=value argument in the helm template command.

For example:

$ helm template --name my-odm-prod-release \
  --set internalDatabase.databaseName=my-db \
  --set internalDatabase.user=my-user \
  --set internalDatabase.password=my-password \
  /path/to/ibm-odm-prod-2.1.0.tgz

To customize the helm install with a YAML file

It is also possible to use a custom-made .yaml file to specify the values of the parameters when you install the chart. For example:

$ helm template --name my-odm-prod-release -f myvalues.yaml /path/to/ibm-odm-prod-2.1.0.tgz

Tip: Refer to the sample-values.yaml file to find the default values used by the ibm-odm-prod-2.1.0 chart.

Uninstall a Kubernetes release of Operational Decision Manager

To uninstall and delete a template along with all of the associated releases, use the following command:

$ kubectl delete -f generated-k8s-templates.yaml

Note: The command removes all the Kubernetes components associated with the chart, even Persistent Volume Claims (PVCs), which might contain valuable data.