Update default image to 14.1.2.0

Author: jshum2479

documentation/domains/Domain.json

@@ -466,7 +466,7 @@
           }
         },
         "image": {
-          "description": "The WebLogic Server image; required when `domainHomeSourceType` is Image or FromModel; otherwise, defaults to container-registry.oracle.com/middleware/weblogic:12.2.1.4.",
+          "description": "The WebLogic Server image; required when `domainHomeSourceType` is Image or FromModel; otherwise, defaults to container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8.",
           "type": "string"
         },
         "imagePullPolicy": {

documentation/domains/Domain.md

@@ -28,7 +28,7 @@ The specification of the operation of the WebLogic domain. Required.
 | `fluentbitSpecification` | [Fluentbit Specification](#fluentbit-specification) | Automatic fluent-bit sidecar injection. If specified, the operator will deploy a sidecar container alongside each WebLogic Server instance that runs the fluent-bit, Optionally, the introspector job pod can be enabled to deploy with the fluent-bit sidecar container. WebLogic Server instances that are already running when the `fluentbitSpecification` field is created or deleted, will not be affected until they are restarted. When any given server is restarted for another reason, such as a change to the `restartVersion`, then the newly created pod  will have the fluent-bit sidecar or not, as appropriate |
 | `fluentdSpecification` | [Fluentd Specification](#fluentd-specification) | Automatic fluentd sidecar injection. If specified, the operator will deploy a sidecar container alongside each WebLogic Server instance that runs the fluentd, Optionally, the introspector job pod can be enabled to deploy with the fluentd sidecar container. WebLogic Server instances that are already running when the `fluentdSpecification` field is created or deleted, will not be affected until they are restarted. When any given server is restarted for another reason, such as a change to the `restartVersion`, then the newly created pod  will have the fluentd sidecar or not, as appropriate |
 | `httpAccessLogInLogHome` | Boolean | Specifies whether the server HTTP access log files will be written to the same directory specified in `logHome`. Otherwise, server HTTP access log files will be written to the directory configured in the WebLogic domain configuration. Defaults to true. |
-| `image` | string | The WebLogic Server image; required when `domainHomeSourceType` is Image or FromModel; otherwise, defaults to container-registry.oracle.com/middleware/weblogic:12.2.1.4. |
+| `image` | string | The WebLogic Server image; required when `domainHomeSourceType` is Image or FromModel; otherwise, defaults to container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8. |
 | `imagePullPolicy` | string | The image pull policy for the WebLogic Server image. Legal values are Always, Never, and IfNotPresent. Defaults to Always if image ends in :latest; IfNotPresent, otherwise. |
 | `imagePullSecrets` | Array of [Local Object Reference](k8s1.28.2.md#local-object-reference) | A list of image pull Secrets for the WebLogic Server image. |
 | `includeServerOutInPodLog` | Boolean | Specifies whether the server .out file will be included in the Pod's log. Defaults to true. |

documentation/site/content/base-images/custom-images.md

@@ -239,7 +239,7 @@ see [Container image protection]({{<relref "/security/domain-security/image-prot
 
 {{% notice warning %}}
 The sample scripts in this section reference base image
-`container-registry.oracle.com/middleware/weblogic:12.2.1.4`.
+`container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8`.
 This is an OCR General Availability (GA) image
 which **does not include** the latest security patches for WebLogic Server.
 GA images are intended for single desktop demonstration and development purposes _only_.
@@ -312,7 +312,7 @@ to create the domain home in Domain in Image.
 
   # Define base image and final image
 
-  fromImage=container-registry.oracle.com/middleware/weblogic:12.2.1.4
+  fromImage=container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8
   finalImage=my-dii-wdt:v1
 
   # Init staging directory
@@ -414,7 +414,7 @@ to create the domain home in Domain in Image.
 
   # Define base image and final image
 
-  fromImage=container-registry.oracle.com/middleware/weblogic:12.2.1.4
+  fromImage=container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8
   finalImage=my-dii-wlst:v1
 
   # Copy sample WLST, Docker commands, and setup scripts
@@ -489,7 +489,7 @@ to create the domain home in Domain in Image.
 
 {{% notice warning %}}
 The example in this section references a base image,
-`container-registry.oracle.com/middleware/weblogic:12.2.1.4`.
+`container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8`.
 This is an OCR General Availability (GA) image
 which **does not include** the latest security patches for WebLogic Server.
 GA images are intended for single desktop demonstration and development purposes _only_.
@@ -524,7 +524,7 @@ Example steps for creating a custom WebLogic image with a Model in Image file la
    See [Obtain images from the Oracle Container Registry]({{< relref "/base-images/ocr-images#obtain-images-from-the-oracle-container-registry" >}})
    or [Create a custom image with patches applied](#create-a-custom-image-with-patches-applied).
 
-   In the following step, you will use the `container-registry.oracle.com/middleware/weblogic:12.2.1.4` GA image.
+   In the following step, you will use the `container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8` GA image.
 
 1. Build the final image using WIT while specifying the base image, target image tag, WDT installation location,
    and WDT model file locations. For example:
@@ -550,7 +550,7 @@ Example steps for creating a custom WebLogic image with a Model in Image file la
    ```shell
    $ ./imagetool/bin/imagetool.sh update \
      --tag wdt-domain-image:WLS-LEGACY-v1 \
-     --fromImage container-registry.oracle.com/middleware/weblogic:12.2.1.4 \
+     --fromImage container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8 \
      --wdtModel      ./model.10.yaml \
      --wdtVariables  ./model.10.properties \
      --wdtArchive    ./archive.zip \

documentation/site/content/introduction/architecture.md

@@ -130,7 +130,7 @@ The following diagram shows the components inside the containers running WebLogi
 
 {{< img "Inside a container" "images/inside-a-container.png" >}}
 
-The Domain specifies a container image, defaulting to `container-registry.oracle.com/middleware/weblogic:12.2.1.4`. All containers running WebLogic Server use this same image. Depending on the use case, this image could contain the WebLogic Server product binaries or also include the domain directory. For detailed information about domain images, see [WebLogic images]({{< relref "/base-images/_index.md" >}}).
+The Domain specifies a container image, defaulting to `container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8`. All containers running WebLogic Server use this same image. Depending on the use case, this image could contain the WebLogic Server product binaries or also include the domain directory. For detailed information about domain images, see [WebLogic images]({{< relref "/base-images/_index.md" >}}).
 
 {{% notice warning %}}
 The default image is a General Availability image. GA images are suitable for demonstration and development purposes _only_ where the environments are not available from the public Internet; they are **not acceptable for production use**. In production, you should always use CPU (patched) images from [OCR]({{< relref "/base-images/ocr-images.md" >}}) or create your images using the [WebLogic Image Tool]({{< relref "/base-images/custom-images#create-a-custom-base-image" >}}) (WIT) with the `--recommendedPatches` option. For more guidance, see [Apply the Latest Patches and Updates](https://www.oracle.com/pls/topic/lookup?ctx=en/middleware/standalone/weblogic-server/14.1.1.0&id=LOCKD-GUID-2DA84185-46BA-4D7A-80D2-9D577A4E8DE2) in _Securing a Production Environment for Oracle WebLogic Server_.

documentation/site/content/introduction/prerequisites/introduction.md

@@ -26,7 +26,7 @@ Support for Kubernetes 1.32.1+ with Oracle WebLogic Server 12.2.1.4 or 14.1.1.0
    {{% notice warning %}}
    Throughout the documentation, the sample images are General Availability (GA) images. GA images are suitable for demonstration and development purposes _only_ where the environments are not available from the public Internet; they are **not acceptable for production use**. In production, you should always use CPU (patched) images from [OCR]({{< relref "/base-images/ocr-images.md" >}}) or create your images using the [WebLogic Image Tool]({{< relref "/base-images/custom-images#create-a-custom-base-image" >}}) (WIT) with the `--recommendedPatches` option. For more guidance, see [Apply the Latest Patches and Updates](https://www.oracle.com/pls/topic/lookup?ctx=en/middleware/standalone/weblogic-server/14.1.1.0&id=LOCKD-GUID-2DA84185-46BA-4D7A-80D2-9D577A4E8DE2) in _Securing a Production Environment for Oracle WebLogic Server_. For details on how to obtain or create images, see [WebLogic images]({{< relref "/base-images/_index.md" >}}).
    {{% /notice %}}
-   * Check the WLS version and patches using the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/userguide/tools/inspect-image/) `inspect` command: `imagetool inspect --image=container-registry.oracle.com/middleware/weblogic:12.2.1.4 --patches`. For more information, see [Inspect images]({{< relref "/base-images/ocr-images#inspect-images" >}}).
+   * Check the WLS version and patches using the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/userguide/tools/inspect-image/) `inspect` command: `imagetool inspect --image=container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8 --patches`. For more information, see [Inspect images]({{< relref "/base-images/ocr-images#inspect-images" >}}).
 * Container images based on Oracle Linux 8 are now supported. The Oracle Container Registry hosts container images
   based on both Oracle Linux 7 and 8, including Oracle WebLogic Server 14.1.1.0.0 images based on Java 8 and 11 and Oracle WebLogic Server 14.1.2.0.0 images based on Java 17 and 21.
 * Container images based on Oracle Linux 9 are now supported. The Oracle Container Registry hosts container images

documentation/site/content/managing-domains/cicd/layering.md

@@ -8,7 +8,7 @@ description: "Learn about container image layering and why it is important."
 
 Container images are composed of layers, as shown in the following diagram.  If you download
 the standard `weblogic:12.2.1.4` image from the [Oracle Container Registry](https://container-registry.oracle.com),
-then you can see these layers using the command  `docker inspect container-registry.oracle.com/middleware/weblogic:12.2.1.4`
+then you can see these layers using the command  `docker inspect container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8`
 (the domain layer will not be there).  You are not required to use layers, but
 efficient use of layers is considered a best practice.
 

documentation/site/content/managing-domains/domain-resource.md

@@ -124,7 +124,7 @@ The Domain `spec` section contains elements for configuring the domain operation
 Elements related to domain identification, container image, and domain home:
 
 * `domainUID`: Domain unique identifier. This identifier is required to be no more than 45 characters (for more details, see [Meet Kubernetes resource name restrictions]({{< relref "/managing-domains/manage-domains#meet-kubernetes-resource-name-restrictions" >}}). It is recommended that this value be unique to assist in future work to identify related domains in active-passive scenarios across data centers; however, it is only required that this value be unique within the namespace, similarly to the names of Kubernetes resources. This value is distinct and need not match the domain name from the WebLogic domain configuration. Defaults to the value of `metadata.name`.
-* `image`: The WebLogic container image; required when `domainHomeSourceType` is Image or FromModel (when not specifying an auxiliary image); otherwise, defaults to `container-registry.oracle.com/middleware/weblogic:12.2.1.4`. **WARNING**: The default image is unpatched and therefore, should always be specified to use an image with the latest patches installed (for example, `container-registry.oracle.com/middleware/weblogic_cpu:12.2.1.4-slim-jdk8-ol8`). For more information, see [Understand Oracle Container Registry images]({{< relref "/base-images/ocr-images#understand-oracle-container-registry-images" >}}).
+* `image`: The WebLogic container image; required when `domainHomeSourceType` is Image or FromModel (when not specifying an auxiliary image); otherwise, defaults to `container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8`. **WARNING**: The default image is unpatched and therefore, should always be specified to use an image with the latest patches installed (for example, `container-registry.oracle.com/middleware/weblogic_cpu:12.2.1.4-slim-jdk8-ol8`). For more information, see [Understand Oracle Container Registry images]({{< relref "/base-images/ocr-images#understand-oracle-container-registry-images" >}}).
 * `imagePullPolicy`: The image pull policy for the WebLogic container image. Legal values are Always, Never, and IfNotPresent. Defaults to Always if the image ends in `:latest`; IfNotPresent, otherwise. To ensure that all nodes have the same image, any images that are updated without changing the tag should be set to Always.
 * `imagePullSecrets`: A list of image pull Secrets for the WebLogic container image.
 * `domainHome`: The directory containing the WebLogic domain configuration inside the container. Defaults to /shared/domains/domains/<domainUID> if `domainHomeSourceType` is PersistentVolume. Defaults to /u01/oracle/user_projects/domains/ if `domainHomeSourceType` is Image. Defaults to /u01/domains/<domainUID> if `domainHomeSourceType` is FromModel.

documentation/site/content/managing-domains/managing-fmw-domains.md

@@ -70,13 +70,13 @@ $ docker login container-registry.oracle.com
 Then, you can pull the image with this command:
 
 ```shell
-$ docker pull container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.4
+$ docker pull container-registry.oracle.com/middleware/fmw-infrastructure:14.1.2.0-jdk17-ol8
 ```
 If desired, you can:
 
-* Check the WLS version with `docker run container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.4 sh -c` `'source $ORACLE_HOME/wlserver/server/bin/setWLSEnv.sh > /dev/null 2>&1 && java weblogic.version'`
+* Check the WLS version with `docker run container-registry.oracle.com/middleware/fmw-infrastructure:14.1.2.0-jdk17-ol8 sh -c` `'source $ORACLE_HOME/wlserver/server/bin/setWLSEnv.sh > /dev/null 2>&1 && java weblogic.version'`
 
-* Check the WLS patches with `docker run container-registry.oracle.com/middleware/fmw-infrastructure:12.2.1.4 sh -c` `'$ORACLE_HOME/OPatch/opatch lspatches'`
+* Check the WLS patches with `docker run container-registry.oracle.com/middleware/fmw-infrastructure:14.1.2.0-jdk17-ol8 sh -c` `'$ORACLE_HOME/OPatch/opatch lspatches'`
 
 Additional information about using this image is available in the
 [Oracle Container Registry](https://container-registry.oracle.com).

documentation/site/content/managing-domains/model-in-image/usage.md

@@ -18,7 +18,7 @@ Deploy the operator and ensure that it is monitoring the desired namespace for y
 
 Model in Image requires an image with a WebLogic Server installation.
 
-- You can start with WebLogic Server 12.2.1.4 or later, an Oracle Container Registry pre-built base image, such as `container-registry.oracle.com/middleware/weblogic:12.2.1.4`.
+- You can start with WebLogic Server 12.2.1.4 or later, an Oracle Container Registry pre-built base image, such as `container-registry.oracle.com/middleware/weblogic:14.1.2.0-generic-jdk17-ol8`.
   {{% notice note %}}
   The images in `container-registry.oracle.com/middleware/weblogic` are unpatched images. You should always either use patched images from `container-registry.oracle.com/middleware/weblogic_cpu` or build your own patched images (see [Create a custom image with patches applied]({{< relref "/base-images/custom-images#create-a-custom-image-with-patches-applied" >}})).
   {{% /notice %}}

documentation/site/content/quickstart/create-domain.md

@@ -46,7 +46,7 @@ weight: 3
      - For detailed information, see [Domain resource]({{< relref "/managing-domains/domain-resource.md" >}}).
 
    {{% notice note %}}
-   The Quick Start guide's sample domain resource references a WebLogic Server version 12.2.1.4 General Availability (GA) image. GA images are suitable for demonstration and development purposes _only_ where the environments are not available from the public Internet; they are **not acceptable for production use**. In production, you should always use CPU (patched) images from [OCR]({{< relref "/base-images/ocr-images.md" >}}) or create your images using the [WebLogic Image Tool]({{< relref "/base-images/custom-images#create-a-custom-base-image" >}}) (WIT) with the `--recommendedPatches` option. For more guidance, see [Apply the Latest Patches and Updates](https://www.oracle.com/pls/topic/lookup?ctx=en/middleware/standalone/weblogic-server/14.1.1.0&id=LOCKD-GUID-2DA84185-46BA-4D7A-80D2-9D577A4E8DE2) in _Securing a Production Environment for Oracle WebLogic Server_.
+   The Quick Start guide's sample domain resource references a WebLogic Server version 14.1.2.0 General Availability (GA) image. GA images are suitable for demonstration and development purposes _only_ where the environments are not available from the public Internet; they are **not acceptable for production use**. In production, you should always use CPU (patched) images from [OCR]({{< relref "/base-images/ocr-images.md" >}}) or create your images using the [WebLogic Image Tool]({{< relref "/base-images/custom-images#create-a-custom-base-image" >}}) (WIT) with the `--recommendedPatches` option. 
    {{% /notice %}}
 
 1.	Confirm that the operator started the servers for the domain.