Verifying the OUDSM Deployment

7.3.4 Verifying the OUDSM Deployment

Run the following command to verify the OUDSM deployment:

kubectl --namespace <namespace> get pod,service,secret,pv,pvc,ingress -o wide

For example:

kubectl --namespace oudsmns get pod,service,secret,pv,pvc,ingress -o wide

The output will look similar to the following:

NAME          READY   STATUS    RESTARTS   AGE   IP            NODE             NOMINATED NODE   READINESS GATES
pod/oudsm-1   1/1     Running   0          73m   10.244.0.19   <worker-node>   <none>           <none>
	
NAME                TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE   SELECTOR
service/oudsm-1     ClusterIP   10.96.108.200   <none>        7001/TCP,7002/TCP   73m   app.kubernetes.io/instance=oudsm,app.kubernetes.io/name=oudsm,oudsm/instance=oudsm-1
service/oudsm-lbr   ClusterIP   10.96.41.201    <none>        7001/TCP,7002/TCP   73m   app.kubernetes.io/instance=oudsm,app.kubernetes.io/name=oudsm
	
NAME                                 TYPE                                  DATA   AGE
secret/orclcred                      kubernetes.io/dockerconfigjson        1      3h13m
secret/oudsm-creds                   opaque                                2      73m
secret/oudsm-token-ksr4g             kubernetes.io/service-account-token   3      73m
secret/sh.helm.release.v1.oudsm.v1   helm.sh/release.v1                    1      73m
	
NAME                            CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                   STORAGECLASS   REASON   AGE   VOLUMEMODE
persistentvolume/oudsm-pv       30Gi       RWX            Retain           Bound    myoudsmns/oudsm-pvc     manual                  73m   Filesystem

NAME                              STATUS   VOLUME     CAPACITY   ACCESS MODES   STORAGECLASS   AGE   VOLUMEMODE
persistentvolumeclaim/oudsm-pvc   Bound    oudsm-pv   30Gi       RWX            manual         73m   Filesystem

NAME                                     HOSTS                               ADDRESS          PORTS   AGE
ingress.extensions/oudsm-ingress-nginx   oudsm-1,oudsm-2,oudsm + 1 more...   100.102.51.230   80      73m

Note:

It will take several minutes before all the services listed above show. While the oudsm pods have a STATUS of 0/1 the pod is started but the OUDSM server associated with it is currently starting. While the pod is starting you can check the startup status in the pod logs, by running the following command:

kubectl logs <pod> -n oudsmns

For example:

kubectl logs oudsm-1 -n oudsmns

If the OUDSM deployment fails, additionally refer to General Troubleshooting for instructions on how describe the failing pod(s). Once the problem is identified follow Deleting an OUDSM Deployment to clean down the deployment before deploying again.

Kubernetes Objects

Kubernetes objects created by the Helm chart are detailed in the table below:

Note:

The ‘Example Name’ for each Object below is based on the value ‘oudsm’ as deployment/release name for the Helm chart installation.

Type	Name	Example Name	Purpose
Service Account	<deployment/release name>	oudsm	Kubernetes Service Account for the Helm Chart deployment.
Secret	<deployment/release name>-creds	oudsm-creds	Secret object for Oracle Unified Directory Services Manager related critical values like passwords.
Persistent Volume	<deployment/release name>-pv	oudsm-pv	Persistent Volume for user_projects mount.
Persistent Volume Claim	<deployment/release name>-pvc	oudsm-pvc	Persistent Volume Claim for user_projects mount.
Pod	<deployment/release name>-N	oudsm-1, oudsm-2, …	Pod(s)/Container(s) for Oracle Unified Directory Services Manager Instances.
Service	<deployment/release name>-N	oudsm-1, oudsm-2, …	Service(s) for HTTP and HTTPS interfaces from Oracle Unified Directory Services Manager instance <deployment/release name>-N.
Ingress	<deployment/release name>-ingress-nginx	oudsm-ingress-nginx	Ingress Rules for HTTP and HTTPS interfaces.