Operator 3.2.4 (#2417)

* Prepare for WKO 3.2.4

README.md

@@ -25,8 +25,8 @@ You can:
 The fastest way to experience the operator is to follow the [Quick Start guide](https://oracle.github.io/weblogic-kubernetes-operator/quickstart/), or you can peruse our [documentation](https://oracle.github.io/weblogic-kubernetes-operator), read our [blogs](https://blogs.oracle.com/weblogicserver/how-to-weblogic-server-on-kubernetes), or try out the [samples](https://oracle.github.io/weblogic-kubernetes-operator/samples/simple/).
 
 ***
-The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.2.3.
-This release was published on May 21, 2021.
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.2.4.
+This release was published on June 18, 2021.
 ***
 
 # Documentation

buildDockerImage.sh

@@ -33,7 +33,7 @@ while getopts "t:" optname; do
   esac
 done
 
-IMAGE_NAME=${name:-ghcr.io/oracle/weblogic-kubernetes-operator:3.2.3}
+IMAGE_NAME=${name:-ghcr.io/oracle/weblogic-kubernetes-operator:3.2.4}
 SCRIPTPATH="$( cd "$(dirname "$0")" > /dev/null 2>&1 ; pwd -P )"
 
 # Proxy settings

buildtime-reports/pom.xml

@@ -8,7 +8,7 @@
     <parent>
         <artifactId>operator-parent</artifactId>
         <groupId>oracle.kubernetes</groupId>
-        <version>3.2.3</version>
+        <version>3.2.4</version>
     </parent>
 
     <artifactId>buildtime-reports</artifactId>

documentation/3.2/content/_index.md

@@ -30,8 +30,8 @@ using the operator to deploy and run a WebLogic domain container-packaged web ap
 ***
 #### Current production release
 
-The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.2.3.
-This release was published on May 21, 2021. See the operator prerequisites and supported environments [here]({{< relref "/userguide/introduction/introduction#operator-prerequisites" >}}).
+The [current release of the operator](https://github.com/oracle/weblogic-kubernetes-operator/releases) is 3.2.4.
+This release was published on June 18, 2021. See the operator prerequisites and supported environments [here]({{< relref "/userguide/introduction/introduction#operator-prerequisites" >}}).
 
 ***
 

documentation/3.2/content/faq/namespace-management.md

@@ -45,7 +45,7 @@ elkIntegrationEnabled: false
 externalDebugHttpPort: 30999
 externalRestEnabled: false
 externalRestHttpsPort: 31001
-image: ghcr.io/oracle/weblogic-kubernetes-operator:3.2.3
+image: ghcr.io/oracle/weblogic-kubernetes-operator:3.2.4
 imagePullPolicy: IfNotPresent
 internalDebugHttpPort: 30999
 javaLoggingLevel: INFO

documentation/3.2/content/quickstart/get-images.md

@@ -10,7 +10,7 @@ weight: 3
 1. Pull the operator image:
 
     ```shell
-    $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.2.3
+    $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.2.4
     ```
 
 1. Pull the Traefik ingress controller image:

documentation/3.2/content/quickstart/install.md

@@ -50,7 +50,7 @@ $ helm install traefik-operator traefik/traefik \
     ```shell
     $ helm install sample-weblogic-operator kubernetes/charts/weblogic-operator \
       --namespace sample-weblogic-operator-ns \
-      --set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.2.3 \
+      --set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.2.4 \
       --set serviceAccount=sample-weblogic-operator-sa \
       --set "enableClusterRoleBinding=true" \
       --set "domainNamespaceSelectionStrategy=LabelSelector" \

documentation/3.2/content/quickstart/prerequisites.md

@@ -12,5 +12,5 @@ The operator uses Helm to create and deploy the necessary resources and then run
 You should clone this repository to your local machine so that you have access to the
 various sample files mentioned throughout this guide:
 ```shell
-$ git clone --branch v3.2.3 https://github.com/oracle/weblogic-kubernetes-operator
+$ git clone --branch v3.2.4 https://github.com/oracle/weblogic-kubernetes-operator
 ```

documentation/3.2/content/release-notes.md

@@ -8,6 +8,7 @@ draft: false
 
 | Date | Version | Introduces backward incompatibilities? | Change |
 | --- | --- | --- | --- |
+| June 18, 2021 | v3.2.4 | no | Resolved several issues related to Istio, diagnostics, and recovery. |
 | May 21, 2021 | v3.2.3 | no | Resolved several issues, including an issue related to preserving the operator-generated internal certificate, corrected the monitoring exporter integration to include the Administration Server, enhanced the model-in-image support to not require the use of configuration overrides, and updated the domain-home-in-image samples to support the WebLogic Image Tool. |
 | April 27, 2021 | v3.2.2 | no | Resolved a set of issues with many related to reducing the operator's network utilization. |
 | April 5, 2021 | v3.2.1 | no | Updated several dependencies, including the Oracle Linux base for the container image. |
@@ -40,6 +41,18 @@ draft: false
 
 ### Change log
 
+#### Operator 3.2.4
+
+* Added support for the sessionAffinity field for the clusterService ([#2383](https://github.com/oracle/weblogic-kubernetes-operator/pull/2383)).
+* Moved several logging messages to the CONFIG level ([#2387](https://github.com/oracle/weblogic-kubernetes-operator/pull/2387)).
+* Resolved an issue related to scalingAction.sh when there were multiple domains in the same namespace ([#2388](https://github.com/oracle/weblogic-kubernetes-operator/pull/2388)).
+* Updated operator logging and related scripts to consistently use ISO-8601 timestamp formatting ([#2386](https://github.com/oracle/weblogic-kubernetes-operator/pull/2386)).
+* Resolved an issue related to monitoring exporter integration and Istio ([#2390](https://github.com/oracle/weblogic-kubernetes-operator/pull/2390)).
+* Additional diagnostics when container start scripts fail to start the WebLogic Server instance ([#2393](https://github.com/oracle/weblogic-kubernetes-operator/pull/2393)).
+* Ensure Kubernetes API failures are logged after the final retry ([#2406](https://github.com/oracle/weblogic-kubernetes-operator/pull/2406)).
+* Resolved an issue related to failing to recover when a node drain or repaving occurred while waiting for the Administration Server to start ([#2398](https://github.com/oracle/weblogic-kubernetes-operator/pull/2398)).
+* Resolved an issue related to Istio and WDT models that use default listen and SSL ports ([#2379](https://github.com/oracle/weblogic-kubernetes-operator/pull/2379)).
+
 #### Operator 3.2.3
 
 * Resolved an issue related to preserving the operator-generated internal certificate ([#2374](https://github.com/oracle/weblogic-kubernetes-operator/pull/2374)).

documentation/3.2/content/samples/simple/azure-kubernetes-service/domain-on-pv.md

@@ -29,7 +29,7 @@ This sample demonstrates how to use the [WebLogic Kubernetes Operator](/weblogic
 Clone the [WebLogic Kubernetes Operator repository](https://github.com/oracle/weblogic-kubernetes-operator) to your machine. We will use several scripts in this repository to create a WebLogic domain. This sample was tested with v3.1.1, but should work with the latest release.
 
 ```shell
-$ git clone --branch v3.2.3 https://github.com/oracle/weblogic-kubernetes-operator.git
+$ git clone --branch v3.2.4 https://github.com/oracle/weblogic-kubernetes-operator.git
 ```
 
 {{% notice info %}} The following sections of the sample instructions will guide you, step-by-step, through the process of setting up a WebLogic cluster on AKS - remaining as close as possible to a native Kubernetes experience. This lets you understand and customize each step. If you wish to have a more automated experience that abstracts some lower level details, you can skip to the [Automation](#automation) section.

documentation/3.2/content/samples/simple/azure-kubernetes-service/model-in-image.md

@@ -30,7 +30,7 @@ This sample demonstrates how to use the [WebLogic Kubernetes Operator](/weblogic
 Clone the [WebLogic Kubernetes Operator repository](https://github.com/oracle/weblogic-kubernetes-operator) to your machine. We will use several scripts in this repository to create a WebLogic domain. This sample was tested with v3.1.1, but should work with the latest release.
 
 ```shell
-$ git clone --branch v3.2.3 https://github.com/oracle/weblogic-kubernetes-operator.git
+$ git clone --branch v3.2.4 https://github.com/oracle/weblogic-kubernetes-operator.git
 ```
 ```shell
 $ cd weblogic-kubernetes-operator

documentation/3.2/content/samples/simple/domains/fmw-domain-home-in-image/_index.md

@@ -121,7 +121,7 @@ The usage of the create script is as follows:
 $ sh create-domain.sh -h
 ```
 ```text
-usage: create-domain.sh -o dir -i file -u username -p password [-q rcuSchemaPassword] [-n encryption-key] [-e] [-v] [-h]
+usage: create-domain.sh -o dir -i file -u username -p password [-q rcuSchemaPassword] [-b buildNetworkParam] [-n encryption-key] [-e] [-v] [-h]
   -i Parameter inputs file, must be specified.
   -o Output directory for the generated YAML files, must be specified.
   -u WebLogic administrator user name for the WebLogic domain.
@@ -130,6 +130,7 @@ usage: create-domain.sh -o dir -i file -u username -p password [-q rcuSchemaPass
   -e Also create the resources in the generated YAML files, optional.
   -v Validate the existence of persistentVolumeClaim, optional.
   -n Encryption key for encrypting passwords in the WDT model and properties files, optional.
+  -b Value to be used in the buildNetwork parameter when invoking WebLogic Image Tool, optional.
   -h Help
 ```
 
@@ -531,3 +532,37 @@ By default, they are installed under `/tmp/dhii-sample/tools` directory.
 ```shell
 $ rm -rf /tmp/dhii-sample/tools/
 ```
+### Troubleshooting
+***Message***: `Failed to build JDBC Connection object`
+
+If the WebLogic Image Tool failed to create a domain and the following error is seen in the output:
+```shell
+Configuring the Service Table DataSource...
+fmwDatabase  jdbc:oracle:thin:@172.18.0.2:30012/devpdb.k8s
+Getting Database Defaults...
+Error: getDatabaseDefaults() failed. Do dumpStack() to see details.
+Error: runCmd() failed. Do dumpStack() to see details.
+Problem invoking WLST - Traceback (innermost last):
+File "/u01/oracle/createFMWDomain.py", line 332, in ?
+File "/u01/oracle/createFMWDomain.py", line 44, in createInfraDomain
+File "/u01/oracle/createFMWDomain.py", line 151, in extendDomain
+File "/tmp/WLSTOfflineIni1609018487056199846.py", line 267, in getDatabaseDefaults
+File "/tmp/WLSTOfflineIni1609018487056199846.py", line 19, in command
+Failed to build JDBC Connection object:
+at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)
+at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:3085)
+at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:738)
+at sun.reflect.GeneratedMethodAccessor131.invoke(Unknown Source)
+at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
+at java.lang.reflect.Method.invoke(Method.java:498)
+
+com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: Got exception when auto configuring the schema component(s) with data obtained from shadow table:
+Failed to build JDBC Connection object:
+```
+
+First, verify that the JDBC connection URL shown in the output is correct. Update the `rcuDatabaseURL` parameter in the inputs YAML file to the correct value if necessary.
+
+If the JDBC connection URL is correct, it is possible that the container in which the WebLogic Image Tool is running for creating a WebLogic domain, is not using the correct networking stack.
+The optional `-b` option in the `create-domain.sh` script can be used to specify the networking mode for the RUN instruction during image build.
+For example, to use the host's network stack, invoke `create-domain.sh` with `-b host`.
+Please refer to Docker Network Settings references for supported networking options.

documentation/3.2/content/samples/simple/domains/model-in-image/prerequisites.md

@@ -23,7 +23,7 @@ weight: 1
    $ cd /tmp
    ```
    ```shell
-   $ git clone --branch v3.2.3 https://github.com/oracle/weblogic-kubernetes-operator.git
+   $ git clone --branch v3.2.4 https://github.com/oracle/weblogic-kubernetes-operator.git
    ```
 
    > **Note**: We will refer to the top directory of the operator source tree as `/tmp/weblogic-kubernetes-operator`; however, you can use a different location.

documentation/3.2/content/samples/simple/tanzu-kubernetes-service/_index.md

@@ -63,7 +63,7 @@ Kubernetes Operators use [Helm](https://helm.sh/) to manage Kubernetes applicati
 Clone the repository.
 
 ```shell
-$ git clone --branch v3.2.3 https://github.com/oracle/weblogic-kubernetes-operator.git
+$ git clone --branch v3.2.4 https://github.com/oracle/weblogic-kubernetes-operator.git
 ```
 ```shell
 $ cd weblogic-kubernetes-operator

documentation/3.2/content/userguide/introduction/architecture.md

@@ -17,7 +17,7 @@ The operator consists of the following parts:
 The operator is packaged in a [container image](https://github.com/orgs/oracle/packages/container/package/weblogic-kubernetes-operator) which you can access using the following `docker pull` commands:  
 
 ```shell
-$ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.2.3
+$ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.2.4
 ```
 
 For more details on acquiring the operator image and prerequisites for installing the operator, consult the [Quick Start guide]({{< relref "/quickstart/_index.md" >}}).

documentation/3.2/content/userguide/introduction/introduction.md

@@ -16,7 +16,7 @@ Detailed instructions are available [here]({{< relref "/userguide/managing-opera
 
 ### Operator prerequisites
 
-For the current production release 3.2.3:
+For the current production release 3.2.4:
 
 * Kubernetes 1.16.15+, 1.17.13+, 1.18.10+, and 1.19.7+ (check with `kubectl version`).
 * Flannel networking v0.9.1-amd64 or later (check with `docker images | grep flannel`), Calico networking v3.16.1 or later,

documentation/3.2/content/userguide/managing-domains/_index.md

@@ -42,7 +42,7 @@ Be aware of the following important considerations for WebLogic domains running
 
 * _Listen Address Overrides:_  The operator will automatically override all WebLogic domain default,
   SSL, admin, or custom channel listen addresses (using situational configuration overrides).  These will become `domainUID` followed by a
-  hyphen and then the server name, all lower case, and underscores converted to hyphens.  For example, if `domainUID=domain1` and
+  hyphen and then the server name, all lowercase, and underscores converted to hyphens.  For example, if `domainUID=domain1` and
   the WebLogic Server name is `Admin_Server`, then its listen address becomes `domain1-admin-server`.
 
 * _Domain, Cluster, Server, and Network-Access-Point Names:_ WebLogic domain, cluster, server, and network-access-point (channel)
@@ -100,7 +100,7 @@ The following is a list of such Kubernetes resources that the operator generates
 * An optional NodePort type service, also known as an external service, for the WebLogic Administration Server named `<domainUID>-<adminServerName>-<externalServiceNameSuffix>`. The default suffix is `-ext`, which can be overridden using the operator's Helm configuration `externalServiceNameSuffix` (see [WebLogic domain management]({{< relref "/userguide/managing-operators/using-the-operator/using-helm#weblogic-domain-management" >}})).
 
 The operator puts in place certain validation checks and conversions to prevent these resources from violating Kubernetes restrictions.
-* All the names previously described can contain only the characters `A-Z`, `a-z`, `0-9`, `-`, or `_`, and must start and end with an alphanumeric character. Note that when generating pod and service names, the operator will convert configured names to lower case and substitute a hyphen (`-`) for each underscore (`_`).
+* All the names previously described can contain only the characters `A-Z`, `a-z`, `0-9`, `-`, or `_`, and must start and end with an alphanumeric character. Note that when generating pod and service names, the operator will convert configured names to lowercase and substitute a hyphen (`-`) for each underscore (`_`).
 * A `domainUID` is required to be no more than 45 characters.
 * WebLogic domain configuration names, such as the cluster names, Administration Server name, and Managed Server names must be kept to a legal length so that the resultant resource names do not exceed Kubernetes' limits.