Updating the OAM Container Image to 14c

Previous Next JavaScript must be enabled to correctly display this content

17.2.8 Updating the OAM Container Image to 14c

You must update the deployment to use the Oracle Access Management (OAM) 14c container image:

Note:

If the upgrade fails, see Restoring After a Failed Upgrade.

Run the following command to update the deployment with the OAM 14c container image:
```
kubectl patch domain %DOMAIN_UID% -n %NAMESPACE% --type merge  -p '{"spec":{"image":"%WEBLOGIC_IMAGE%"}}'
```
For example:
- If using Oracle Container Registry or your own container registry for your OAM container image:
```
kubectl patch domain accessdomain -n oamns --type merge  -p '{"spec":{"image":"container-registry.oracle.com/middleware/oam_cpu:<new_tag>"}}'
```
- If you are not using a container registry and have loaded the image on each of the worker nodes:
```
kubectl patch domain accessdomain -n oamns --type merge  -p '{"spec":{"image":"oracle/oam:14.1.2.1.0"}}'
```
  The output will look similar to the following:
```
domain.weblogic.oracle/accessdomain patched
```