add doc for applying patched images (#2318)

Author: rosemarymarano

documentation/staging/content/userguide/managing-domains/apply-patched-images.md

@@ -0,0 +1,58 @@
++++
+title = "Apply patched binary images to a running domain"
+date = 2019-02-23T16:43:45-05:00
+weight = 9
+pre = "<b> </b>"
++++
+
+
+When updating WebLogic binaries of a running domain in Kubernetes with a patched container image,
+the operator applies the update in a Zero Downtime (ZDT) fashion. The procedure for the operator
+to update the running domain differs depending on the [domain home source type]({{< relref "/userguide/managing-domains/choosing-a-model/_index.md" >}}).
+
+For Domain in PV, the operator can apply the update to the running domain without modifying the patched container image. For Model in Image (MII) and Domain in Image,
+before the operator can apply the update, the patched container images need to be modified to add the domain home or a
+WebLogic Deploy Tooling (WDT) model and archive. You use the WebLogic Image Tool (WIT) to update or rebase a patched
+container image with a WDT model or with a domain inside of the image.
+
+In all three domain home source types, you edit the [Domain Resource]({{< relref "/userguide/managing-domains/domain-resource#domain-resource-attribute-references" >}})
+to inform the operator of the name of the new patched image so that it can manage the update of the WebLogic domain.
+
+##### Domain in PV
+
+Edit the Domain Resource image reference with the new image name/tag (for example, `oracle/weblogic:12.2.1.4-patched`).
+Then, the operator performs a rolling restart of the WebLogic domain to update the Oracle Home of the servers.
+
+##### Model in Image
+Use WIT [Update Image](https://github.com/oracle/weblogic-image-tool/blob/master/site/update-image.md) to extend patched container images with a WDT model and application archive file.
+Then, the operator performs a rolling update of the domain, updating the ORACLE HOME of each server pod in a ZDT fashion.
+
+For example:
+
+Update an image, `oracle/weblogic:12.2.1.4-patched`, to create an MII image tagged `mydomain:v2`,
+which includes a WDT model file, `./wdt/my_domain.yaml`, and a WDT archive, `./wdt/my_domain.zip`.
+
+```shell
+$imagetool update --fromImage oracle/weblogic:12.2.1.4-patched --wdtModelOnly
+--tag mydomain:v2 --wdtArchive ./wdt/my_domain.zip --wdtModel ./wdt/my_domain.yaml --wdtVersion latest
+```
+
+Then, edit the Domain Resource image reference with the new image name/tag (`mydomain:2`).
+
+##### Domain in Image
+Use WIT [Rebase Image](https://github.com/oracle/weblogic-image-tool/blob/master/site/rebase-image.md) to update the Oracle Home
+for an existing domain image using the patched Oracle Home from a patched container image. Then, the operator performs a rolling update
+of the domain, updating the Oracle Home of each server pod in a ZDT fashion.
+
+For example:
+
+WIT copies the domain from the source image, `mydomain:v1`, to a new image, `mydomain:v2`, based on a target
+image named `oracle/weblogic:12.2.1.4-patched`.
+
+**Note**: On each image, Oracle Home and the JDK must be installed in the same directories.
+
+```shell
+$imagetool rebase --tag mydomain:v2 --sourceImage mydomain:v1 --targetImage oracle/weblogic:12.2.1.4-patched
+```
+
+Then, edit the Domain Resource image reference with the new image name/tag (`mydomain:2`).

documentation/staging/content/userguide/managing-domains/domain-events.md

@@ -1,7 +1,7 @@
 +++
 title = "Domain events"
 date = 2020-11-30T16:43:45-05:00
-weight = 9
+weight = 10
 pre = "<b> </b>"
 +++
 
@@ -40,11 +40,12 @@ The operator also generates these event types in the operator's namespace, which
 *  `StopManagingNamespace`: The operator has stopped managing domains in a namespace. 
 *  `StartManagingNamespaceFailed`: The operator failed to start managing domains in a namespace because it does not have the required privileges.
 
+
 #### Operator-generated event details
 
 Each operator-generated event contains the following fields:
  *  `metadata`
-    *  `namespace`:  Namespace in which the event is generated. 
+    *  `namespace`:  Namespace in which the event is generated.
     *  `labels`:   `weblogic.createdByOperator=true` and, for a domain event, `weblogic.domainUID=<domainUID>`.
  *  `type`:  String that describes the type of the event. Possible values are `Normal` or `Warning`.
  *  `count`: Integer that indicates the number of occurrences of the event. Note that the events are matched by the combination of the `reason`, `involvedObject`, and `message` fields.
@@ -60,7 +61,7 @@ Each operator-generated event contains the following fields:
     *  `kind`:  String that describes the kind of resource this object represents. The value is `Domain` for a domain event, `Namespace` for a namespace event in the domain namespace, or `Pod` for the operator pod.
     *  `apiVersion`:  String that describes the `apiVersion` of the involved object, which is the `apiVersion` of the domain resource, for example, `weblogic.oracle/v8`, for a domain event or unset for a namespace event.
     *  `UID`: String that describes the unique identifier of the object that is generated by the Kubernetes server.
-    
+
 #### How to access the events
 
 To access the events that are associated with all resources in a particular namespace, run:
@@ -214,7 +215,7 @@ LAST SEEN   TYPE      REASON                      OBJECT
 5m43s       Warning   DomainProcessingFailed      domain/sample-domain1                   Failed to complete processing domain resource sample-domain1 due to: Job sample-domain1-introspector failed due to reason: DeadlineExceeded. ActiveDeadlineSeconds of the job is configured with 120 seconds. The job was started 120 seconds ago. Ensure all domain dependencies have been deployed (any secrets, config-maps, PVs, and PVCs that the domain resource references). Use kubectl describe for the job and its pod for more job failure information. The job may be retried by the operator up to 5 times with longer ActiveDeadlineSeconds value in each subsequent retry. Use tuning parameter domainPresenceFailureRetryMaxCount to configure max retries., the processing will be retried if needed
 5m43s       Normal    SuccessfulDelete            job/sample-domain1-introspector         Deleted pod: sample-domain1-introspector-d42rf
 5m32s       Normal    Scheduled                   pod/sample-domain1-introspector-cmxjs   Successfully assigned sample-domain1-ns/sample-domain1-introspector-cmxjs to doxiao-1
-5m32s       Normal    SuccessfulCreate            job/sample-domain1-introspector         Created pod: sample-domain1-introspector-cmxjs 
+5m32s       Normal    SuccessfulCreate            job/sample-domain1-introspector         Created pod: sample-domain1-introspector-cmxjs
 4m52s       Normal    Pulling                     pod/sample-domain1-introspector-cmxjs   Pulling image "domain-home-in-image:12.2.1.4"
 4m50s       Warning   Failed                      pod/sample-domain1-introspector-cmxjs   Failed to pull image "domain-home-in-image:12.2.1.4": rpc error: code = Unknown desc = pull access denied for domain-home-in-image, repository does not exist or may require 'docker login'
 4m50s       Warning   Failed                      pod/sample-domain1-introspector-cmxjs   Error: ErrImagePull