Completing post-deployment tasks

After you install an Operational Decision Manager release, you want to verify its deployment.

1. Check the status of the pods that are created by running the following command.

   $ kubectl get pods

   Table 1. Status of pods

   NAME	READY	STATUS	RESTARTS	AGE
   my-odm-prod-release-dbserver-*** (only present when you use an internal database)	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

2. When all of the pods are Running and Ready, run the following command to display useful information to connect to the Operational Decision Manager applications.

   $ helm status release_name

   The command returns the following information:

   • The last deployment time.
   • The Kubernetes namespace where the release lives.
   • The state of the release: unknown, deployed, uninstalled, superseded, failed, uninstalling, pending-install, pending-upgrade, or pending-rollback.
   • Details about the last test suite run, if applicable.
   • Extra notes provided by the Helm chart.
3. Retrieve the external access point.

   There are three mechanisms by which you can access your Operational Decision Manager applications in a Certified Kubernetes cluster: OpenShift routes, Ingress, or NodePort. For more information, see Configuring external access.