Performing the Upgrade Within 14.1.2

13.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 (OUD) Kubernetes deployment with a new OUD 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.
If you have Kubernetes Horizontal Pod Autoscaler (HPA) enabled, you must disable HPA before performing the steps below. See, Deleting the Horizontal Pod Autoscaler.

Navigate to the $WORKDIR/kubernetes/helm14c directory:
```
cd $WORKDIR/kubernetes/helm14c
```
Create an oud-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/oud_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 OUD container image, then you can remove the following:
```
imagePullSecrets:
  - name: orclcred
```
If you have also upgraded your version of Kubernetes since the last container image update, you also need to add the following to the file:
```
cronJob:
  kubectlImage:
    repository: bitnami/kubectl
    tag: <version>
    pullPolicy: IfNotPresent
```
Where the <version> in kubectlImage: tag: should be set to the same version as your Kubernetes version (kubectl version). For example if your Kubernetes version is 1.30.3 set to 1.30.3.
If your cluster does not have access to the internet to pull the bitnami/kubectl image, you must load the images in a local container registry and set the repository tag appropriately.

Take a backup of the persistent volume directory:

sudo cp -rp <persistent_volume>/oud_user_projects <persistent_volume>/oud_user_projects_bkp14c_<tag>

For example:

sudo cp -rp /nfs_volumes/oudpv/oud_user_projects /nfs_volumes/oudpv/oud_user_projects_bkp14c_old

Run the following command to upgrade the deployment:

helm upgrade --namespace <namespace> \
--values oud-patch-override.yaml \
<release_name> oud-ds-rs --reuse-values

For example:

helm upgrade --namespace oudns \
--values oud-patch-override.yaml \
oud-ds-rs oud-ds-rs --reuse-values

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

Run the following command and make sure all the OUD 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 oudns -w
```
You can also tail the logs for the pods by running:
```
kubectl logs -f <pod> -n oudns
```

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

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

For example:

kubectl describe pod oud-ds-rs-0 -n oudns | grep image

The output will look similar to the following:

...
Containers:
  oud-ds-rs:
    Container ID:   cri-o://6a35ef3a0721015aa99b2aaeebdc96528c8166db7bf36176f0b9665e43c10ded
    Image:          container-registry.oracle.com/middleware/oud_cpu:14.1.2.1.0-jdk17-ol8-<YYMMDD>
    Image ID:       container-registry.oracle.com/middleware/oud_cpu@sha256:2ae38d6bdca4c411d6b62289cf80563f611a1fdcbaf01632be7b4fa6a4169000

Verify the OUD deployment where applicable: