As per the Prerequisites a Kubernetes cluster should have already been configured.
Run the following command on the master node to check the cluster and worker nodes are running:
$ kubectl get nodes,pods -n kube-system
The output will look similar to the following:
NAME STATUS ROLES AGE VERSION node/worker-node1 Ready <none> 17h v1.26.6+1.el8 node/worker-node2 Ready <none> 17h v1.26.6+1.el8 node/master-node Ready master 23h v1.26.6+1.el8 NAME READY STATUS RESTARTS AGE pod/coredns-66bff467f8-fnhbq 1/1 Running 0 23h pod/coredns-66bff467f8-xtc8k 1/1 Running 0 23h pod/etcd-master 1/1 Running 0 21h pod/kube-apiserver-master-node 1/1 Running 0 21h pod/kube-controller-manager-master-node 1/1 Running 0 21h pod/kube-flannel-ds-amd64-lxsfw 1/1 Running 0 17h pod/kube-flannel-ds-amd64-pqrqr 1/1 Running 0 17h pod/kube-flannel-ds-amd64-wj5nh 1/1 Running 0 17h pod/kube-proxy-2kxv2 1/1 Running 0 17h pod/kube-proxy-82vvj 1/1 Running 0 17h pod/kube-proxy-nrgw9 1/1 Running 0 23h pod/kube-scheduler-master 1/1 Running 0 21$
The Oracle Unified Directory Services Manager (OUDSM) Kubernetes deployment requires access to an OUDSM container image. The image can be obtained in the following ways:
The prebuilt OUDSM April 2023 container image can be downloaded from Oracle Container Registry. This image is prebuilt by Oracle and includes Oracle Unified Directory Services Manager 184.108.40.206.0, the April Patch Set Update (PSU) and other fixes released with the Critical Patch Update (CPU) program..
Note: Before using this image you must login to Oracle Container Registry, navigate to
oudsm_cpu and accept the license agreement.
You can use this image in the following ways:
You can build your own OUDSM container image using the WebLogic Image Tool. This is recommended if you need to apply one off patches to a Prebuilt OUDSM container image. For more information about building your own container image with WebLogic Image Tool, see Create or update image
You can use an image built with WebLogic Image Tool in the following ways:
Note: This documentation does not tell you how to pull or push the above images into a private container registry, or stage them on the master and worker nodes. Details of this can be found in the Enterprise Deployment Guide.
Oracle Unified Directory Services Manager deployment on Kubernetes leverages deployment scripts provided by Oracle for creating Oracle Unified Directory Services Manager containers using the Helm charts provided. To deploy Oracle Unified Directory Services Manager on Kubernetes you should set up the deployment scripts on the master node as below:
Create a working directory to setup the source code.
$ mkdir <workdir>
$ mkdir /scratch/OUDSMContainer
Download the latest OUDSM deployment scripts from the OUDSM repository:
$ cd <workdir> $ git clone https://github.com/oracle/fmw-kubernetes.git
$ cd /scratch/OUDSMContainer $ git clone https://github.com/oracle/fmw-kubernetes.git
$WORKDIR environment variable as follows:
$ export WORKDIR=<workdir>/fmw-kubernetes/OracleUnifiedDirectorySM
$ export WORKDIR=/scratch/OUDSMContainer/fmw-kubernetes/OracleUnifiedDirectorySM
You are now ready to create the OUDSM deployment as per Create OUDSM instances.