Choose one of the following options to update your OAM kubernetes cluster to use the new image:
kubectl edit domain
commandkubectl patch domain
commandIn all of the above cases, the WebLogic Kubernetes Operator will restart the Administration Server pod first and then perform a rolling restart on the OAM Managed Servers.
Note: 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.
To update the domain with the kubectl edit domain
command, run the following:
$ kubectl edit domain <domainname> -n <namespace>
For example:
$ kubectl edit domain accessdomain -n oamns
If using Oracle Container Registry or your own container registry for your OAM container image, update the image
to point at the new image, for example:
domainHomeInImage: false
image: container-registry.oracle.com/middleware/oam_cpu:<tag>
imagePullPolicy: IfNotPresent
If you are not using a container registry and have loaded the image on each of the master and worker nodes, update the image
to point at the new image:
domainHomeInImage: false
image: oracle/oam:<tag>
imagePullPolicy: IfNotPresent
Save the file and exit (:wq!)
To update the domain with the kubectl patch domain
command, run the following:
$ kubectl patch domain <domain> -n <namespace> --type merge -p '{"spec":{"image":"newimage:tag"}}'
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:<tag>"}}'
For example, if you are not using a container registry and have loaded the image on each of the master and worker nodes:
$ kubectl patch domain accessdomain -n oamns --type merge -p '{"spec":{"image":"oracle/oam:<tag>"}}'
The output will look similar to the following:
domain.weblogic.oracle/accessdomain patched