Performing the Upgrade Within 14.1.2

12.1.1 Performing the Upgrade Within 14.1.2

Run the following steps to patch or upgrade an existing 14.1.2.1.0 Oracle Unified Directory Services Manager (OUDSM) Kubernetes deployment with a new OUDSM 14c container image:

Note:

Administrators should be aware of the following:

If you are not using Oracle Container Registry or your own container registry, then you must first load the new container image on all nodes in your Kubernetes cluster.

Navigate to the $WORKDIR/kubernetes/helm14c directory:
```
cd $WORKDIR/kubernetes/helm14c
```

Create an oudsm-patch-override.yaml file that contains:

image:
  repository: <image_location>
  tag: <image_tag>
 imagePullSecrets:
   - name: orclcred

For example:

image:
  repository: container-registry.oracle.com/middleware/oudsm_cpu
  tag: 14.1.2.1.0-jdk17-ol8-<YYMMDD>
imagePullSecrets:
  - name: orclcred

Note:

If you are not using Oracle Container Registry or your own container registry for your OUDSM container image, then you can remove the following:

imagePullSecrets:
  - name: orclcred

Take a backup of the persistent volume directory:

sudo cp -rp <persistent_volume>/oudsm_user_projects <persistent_volume>/oudsm_user_projects_bkp14c_<tag>

For example:

sudo cp -rp /nfs_volumes/oudsmpv/oudsm_user_projects /nfs_volumes/oudsmpv/oudsm_user_projects_bkp14c_old

Run the following command to upgrade the deployment:

helm upgrade --namespace <namespace> \
--values oudsm-patch-override.yaml \
<release_name> oudsm --reuse-values

For example:

helm upgrade --namespace oudsmns \
--values oudsm-patch-override.yaml \
oudsm oudsm --reuse-values

The helm upgrade will perform a rolling restart of the OUDSM pods.

Run the following command and make sure all the OUDSM pods are started:
```
kubectl get pods -n <namespace> -w
```
Note:
The -w flag allows you watch the status of the pods as they change.
For example:
```
kubectl get pods -n oudsmns -w
```
You can also tail the logs for the pods by running:
```
kubectl logs -f <pod> -n oudsmns
```

Once the pods are up and running, you can run the following command to show the new OUDSM 14c container image is used by the pods:

kubectl describe pod <pod> -n <namespace> | grep image

For example:

kubectl describe pod oudsm-1 -n oudsmns | grep image

The output will look similar to the following:

...
Containers:
  oudsm-1:
    Container ID:   cri-o://6a35ef3a0721015aa99b2aaeebdc96528c8166db7bf36176f0b9665e43c10ded
    Image:          container-registry.oracle.com/middleware/oudsm_cpu:14.1.2.1.0-jdk17-ol8-<YYMMDD>
    Image ID:       container-registry.oracle.com/middleware/oudsm_cpu@sha256:2ae38d6bdca4c411d6b62289cf80563f611a1fdcbaf01632be7b4fa6a4169000

Verify the OUDSM deployment. See, Validating OUDSM URLs.