Upgrading from OHS 12.2.1.4 to OHS 14.1.2

10.2 Upgrading from OHS 12.2.1.4 to OHS 14.1.2

Learn how to upgrade from Oracle HTTP Server (OHS) 12.2.1.4 to OHS 14.1.2.

The instructions in this section relate to upgrading an existing 12.2.1.4 OHS deployment to OHS 14.1.2.

Take a backup of your existing OHS configuration files in $MYOHSFILES.
Read What’s New in this Release and look at the New Features and Deprecated Features in 14.1.2. Make any required changes to your OHS configuration files in $MYOHSFILES/ohsConfig.
Delete any ConfigMaps that relate to any files you have changed. For example if you have changed httpd.conf and files in moduleconf, run:
```
kubectl delete cm ohs-httpd -n ohsns
kubectl delete cm ohs-config -n ohsns
```

Recreate the required ConfigMaps:

cd $MYOHSFILES
kubectl create cm -n ohsns ohs-httpd --from-file=ohsConfig/httpconf
kubectl create cm -n ohsns ohs-config --from-file=ohsConfig/moduleconf

Edit the $MYOHSFILES/ohs.yaml and change the <IMAGE_NAME> to the correct 14.1.2 image tag on Oracle Container Registry. If you are using your own container registry for the image, you will need to change the image location appropriately.

Note:
Before using this image you must login to Oracle Container Registry, navigate to Middleware > ohs and accept the license agreement. For future releases (post January 25) that contain the latest Patch Set Update (PSU) and other fixes released with the Critical Patch Update (CPU) program, you should navigate to Middleware >ohs_cpu.
Find the name of the existing OHS pod:
```
kubectl get pods -n <namespace>
```
For example:
```
kubectl get pods -n ohsns
```
The output will look similar to the following:
```
NAME                         READY   STATUS    RESTARTS   AGE
ohs-domain-d5b648bc5-vkp4s   1/1     Running   0          55s
```
Delete the pod using the following command:
```
kubectl delete pod <pod> -n <namespace>
```
For example:
```
kubectl delete pod ohs-domain-d5b648bc5-vkp4s -n ohsns
```
The output will look similar to the following:
```
pod "ohs-domain-d5b648bc5-vkp4s" deleted
```
Run the following command to make sure the pod has restarted:
```
kubectl get pods -n ohsns
```
The output will look similar to the following:
```
NAME                         READY   STATUS    RESTARTS   AGE
ohs-domain-d5b648bc5-gdvnp   1/1     Running   0          39s
```