Update the doc with the latest patch number plus more doc changes

Signed-off-by: doxiao <[email protected]>

Author: doxiao

kubernetes/samples/scripts/common/domain-template.yaml

@@ -17,7 +17,7 @@ spec:
   domainHome: %DOMAIN_HOME%
   # If the domain home is in the image
   domainHomeInImage: %DOMAIN_HOME_IN_IMAGE%
-  # The Operator currently does not support other images
+  # The WebLogic Server Docker image that the Operator uses to start the domain
   image: "%WEBLOGIC_IMAGE%"
   # imagePullPolicy defaults to "Always" if image version is :latest
   imagePullPolicy: "%WEBLOGIC_IMAGE_PULL_POLICY%"

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md

@@ -1,6 +1,6 @@
 # WebLogic sample domain home in Docker image
 
-The sample scripts demonstrate the creation of a WebLogic domain home in a Docker image. If logHomeOnPV is enabled, then the log home resides on an existing Kubernetes persistent volume (PV) and persistent volume claim (PVC). The scripts also generate the domain YAML file, which can then be used to start the Kubernetes artifacts of the corresponding domain. Optionally, the scripts start up the domain, and WebLogic Server pods and services.
+The sample scripts demonstrate the creation of a WebLogic domain home in a Docker image by using one of the domain home in image samples in the [WebLogic Server Domain Docker image samples GitHub project](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples). The sample scripts have an option of putting the WebLogic domain log, server logs, server output files, and the node manager logs on an existing Kubernetes persistent volume (PV) and persistent volume claim (PVC). The scripts also generate the domain YAML file, which can then be used by the scripts or manually to start the Kubernetes artifacts of the corresponding domain, including the WebLogic Server pods and services.
 
 ## Prerequisites
 
@@ -102,13 +102,13 @@ The following parameters can be provided in the inputs file.
 | `adminServerName` | Name of the Administration Server. | `admin-server` |
 | `clusterName` | Name of the WebLogic cluster instance to generate for the domain. | `cluster-1` |
 | `configuredManagedServerCount` | Number of Managed Server instances to generate for the domain. | `5` |
-| `domainHomeImageBase` | Base WebLogic binary image used to build the WebLogic domain image. The operator requires WebLogic Server 12.2.1.3.0 with patch 29135930 applied. Refer to [Weblogic Docker images](../../../../../site/weblogic-docker-images.md) for details on how to create one. If a different `domainHomeImageBase` is specified, the specified image needs to be built locally or pulled from a repository before the `create-domain.sh` script is executed. | |
+| `domainHomeImageBase` | Base WebLogic binary image used to build the WebLogic domain image. The operator requires WebLogic Server 12.2.1.3.0 with patch 29135930 applied. Refer to [Weblogic Docker images](../../../../../site/weblogic-docker-images.md) for details on how to create one. | |
 | `domainHomeImageBuildPath` | Location of the WebLogic "domain home in image" Docker image in `https://github.com/oracle/docker-images.git` project. If not specified, use "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image". Another possible value is "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image-wdt" which uses WDT, instead of WLST, to generate the domain configuration. | `./docker-images/OracleWebLogic/samples/12213-domain-home-in-image` |
 | `domainPVMountPath` | Mount path of the domain persistent volume. This parameter is required if `logHomeOnPV` is true. Otherwise, it is ignored. | `/shared` |
 | `domainUID` | Unique ID that will be used to identify this particular domain. Used as the name of the generated WebLogic domain as well as the name of the Kubernetes domain resource. This ID must be unique across all domains in a Kubernetes cluster. This ID cannot contain any character that is not valid in a Kubernetes service name. | `domain1` |
 | `exposeAdminNodePort` | Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. | `false` |
 | `exposeAdminT3Channel` | Boolean indicating if the T3 administrative channel is exposed outside the Kubernetes cluster. | `false` |
-| `image` | WebLogic Docker image that the domain resource will pull if needed. You need to specify this only if you are going to tag the generated image to a different name. If you run the sample script from a machine that is remote to the Kubernetes cluster, you need to specify this to point to an image in a registry local to the cluster, and then push the generated image to that registry before starting the domain. If not specified, the sample uses the internally generated image name, either `domain-home-in-image:latest` or `domain-home-in-image-wdt:latest`. | |
+| `image` | WebLogic Server Docker image that the Operator uses to start the domain. The create domain scripts generate a WebLogic Server Docker image with a domain home in it. By default, the scripts tag the generated WebLogic server Docker image as either `domain-home-in-image` or `domain-home-in-image-wdt` based on the `domainHomeImageBuildPath` property, and use it to set the `image` in the generated domain YAML file. If this property is set, the create domain scripts will use the value specified, instead of the default value, to tag the generated image and set the `image` in the domain YAML file. If you are running the sample scripts from a machine that is remote to the Kubernetes cluster where the domain is going to be running, you need to set this property to the image name that is intended to be used in a registry local to that Kubernetes cluster. You also need to push the `image` to that registry before starting the domain using the `kubectl create -f` or `kubectl apply -f` command. | |
 | `imagePullPolicy` | WebLogic Docker image pull policy. Legal values are `IfNotPresent`, `Always`, or `Never`. | `IfNotPresent` |
 | `imagePullSecretName` | Name of the Kubernetes secret to access the Docker Store to pull the WebLogic Server Docker image. The presence of the secret will be validated when this parameter is specified. |  |
 | `includeServerOutInPodLog` | Boolean indicating whether to include `server.out` to the pod's stdout. | `true` |
@@ -160,7 +160,7 @@ spec:
   domainHome: /u01/oracle/user_projects/domains/domain1
   # If the domain home is in the image
   domainHomeInImage: true
-  # The Operator currently does not support other images
+  # The WebLogic Server Docker image that the Operator uses to start the domain
   image: "domain-home-in-image"
   # imagePullPolicy defaults to "Always" if image version is :latest
   imagePullPolicy: "IfNotPresent"

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain-inputs.yaml

@@ -37,17 +37,20 @@ managedServerPort: 8001
 # Boolean indicating if production mode is enabled for the domain
 productionModeEnabled: true
 
-# WebLogic Docker image that the domain resource will pull if needed.
+# WebLogic Server Docker image that the Operator uses to start the domain.
 #
-# You only need to specify this if you want to tag the generated image to a different name.
+# The create domain scripts generate a WebLogic Server Docker image with a domain home in it.
+# By default, the scripts tag the generated WebLogic server Docker image as either
+# `domain-home-in-image` or `domain-home-in-image-wdt` based on the `domainHomeImageBuildPath`
+# property, and use it to set the `image` in the generated domain YAML file.
 #
-# If you are running the sample script from a machine that is remote to the Kubernetes cluster,
-# you need to specify this to point to an image in a registry local to the cluster. You
-# then need to push the generate image to that registry before starting the domain.
-#
-# If not specified, the sample uses the internally generated image name, 
-# either "domain-home-in-image-wdt:latest" or "domain-home-in-image-wlst:latest".
+# If this property is set, the create domain scripts will use the value specified, instead of the
+# default value, to tag the generated image and set the `image` in the domain YAML file.
 #
+# If you are running the sample scripts from a machine that is remote to the Kubernetes cluster where
+# the domain is going to be running, you need to set this property to the image name that is intended
+# to be used in a registry local to that Kubernetes cluster. You also need to push the `image` to
+# that registry before starting the domain using the `kubectl create -f` or `kubectl apply -f` command.
 # See README.md for more help.
 #image: 
 
@@ -116,7 +119,10 @@ persistentVolumeClaimName: domain1-weblogic-sample-pvc
 domainPVMountPath: /shared
 
 # Base WebLogic binary image used to build the WebLogic domain image
-# The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied. 
+# WebLogic Server Docker image.
+# The operator requires WebLogic Server 12.2.1.3.0 with patch 29135930 applied.
+# Refer to [WebLogic Docker images](../../../../../site/weblogic-docker-images.md) for details on how
+# to create a custom Docker image with the required patch.
 # See README.md for more help.
 #domainHomeImageBase: 
 

kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md

@@ -133,7 +133,7 @@ spec:
   domainHome: /shared/domains/domain1
   # If the domain home is in the image
   domainHomeInImage: false
-  # The Operator currently does not support other images
+  # The WebLogic Server Docker image that the Operator uses to start the domain
   image: "oracle/weblogic:12213-patch-wls-for-k8s"
   # imagePullPolicy defaults to "Always" if image version is :latest
   imagePullPolicy: "IfNotPresent"

kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-inputs.yaml

@@ -37,8 +37,10 @@ managedServerNameBase: managed-server
 # Port number for each managed server
 managedServerPort: 8001
 
-# WebLogic Docker image.
-# The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied. See README.md for more help.
+# WebLogic Server Docker image.
+# The operator requires WebLogic Server 12.2.1.3.0 with patch 29135930 applied.
+# Refer to [WebLogic Docker images](../../../../../site/weblogic-docker-images.md) for details on how
+# to create a custom Docker image with the required patch.
 #image:
 
 # Image pull policy