Operator 3.2.5

• Updated the Dockerfile to ensure Oracle Linux libraries are at the latest versions.
• Resolved an issue related to unnecessary repeated introspection (#2418).
• Updated the default monitoring exporter sidecar container image to use the 2.0.3 version.

Operator 3.2.4

• Added support for the sessionAffinity field for the clusterService (#2383).
• Moved several logging messages to the CONFIG level (#2387).
• Resolved an issue related to scalingAction.sh when there were multiple domains in the same namespace (#2388).
• Updated operator logging and related scripts to consistently use ISO-8601 timestamp formatting (#2386).
• Resolved an issue related to monitoring exporter integration and Istio (#2390).
• Additional diagnostics when container start scripts fail to start the WebLogic Server instance (#2393).
• Ensure Kubernetes API failures are logged after the final retry (#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).
• Resolved an issue related to Istio and WDT models that use default listen and SSL ports (#2379).

Operator 3.2.3

• Resolved an issue related to preserving the operator-generated internal certificate #2374.
• Corrected the monitoring exporter integration to include the Administration Server #2365.
• Enhanced the model-in-image support to not require the use of configuration overrides #2344.
• Resolved an issue related to model-in-image domains performing a rolling restart when there had been no change to the model #2348.
• Resolved an issue related to RCU schema password updates #2357.
• Resolved an issue related to namespace starting and stopping events #2345.
• Added support for several new events related to rolling restarts #2364.
• Added support for customer-defined labels and annotations on the operator's pod #2370.

Operator 3.2.2

• Resolved an issue where the operator would retry Kubernetes API requests that timed out without a backoff causing increased network utilization #2300.
• Resolved an issue where the operator would select the incorrect WebLogic Server port for administrative traffic #2301.
• Resolved an issue where the operator, when running in a large and heavily loaded Kubernetes cluster, would not properly detect when a domain had been deleted and recreated #2305 and #2314.
• Resolved an issue where the operator would fail to recover and begin processing in a namespace if the operator did not immediately have privileges in that namespace when it was first detected #2315.
• The operator logs a message when it cannot generate a NamespaceWatchingStopped Event in a namespace because the operator no longer has privileges in that namespace #2323.
• Resolved an issue where the operator would repeatedly replace a ConfigMap causing increased network utilization #2321.
• Resolved an issue where the operator would repeatedly read a Secret causing increased network utilization #2326.
• Resolved an issue where the operator was not honoring domain.spec.adminServer.serverService #2334.

Operator 3.2.1

Updated the versions of several dependencies, including the Oracle Linux base of the container image.

Operator 3.2.0

Features:

• The operator's container image is based on Oracle Linux 8.
• WebLogic Server container images based on Oracle Linux 8 are supported.
• Online updates of dynamic configuration changes for Model in Image.
• Automatic injection of the WebLogic Monitoring Exporter as a sidecar container.
• Events are generated at important moments in the life cycle of the operator or a domain.
• PodDisruptionBudgets are generated for clusters improving the ability to maintain cluster availability during planned node shutdowns and Kubernetes upgrade.
• Additional scripts to assist with common tasks, such as the scaleCluster.sh script.
• Support for TCP and UDP on the same channel when the SIP protocol is used.

Fixes for Bugs or Regressions:

• All fixes included in 3.1.1 through 3.1.4 are included in 3.2.0.
• Resolved an issue where clustered Managed Servers would not start when the Administration Server was not running (#2093)
• Model in Image generated domain home file systems that exceed 1 MB are supported (#2095).
• An event and status update are generated when a cluster can't be scaled past the cluster's maximum size (#2097).
• Improved the operator's ability to recover from failures during its initialization (#2118).
• Improved the ability for scalingAction.sh to discover the latest API version (#2130).
• Resolved an issue where the operator's log would show incorrect warnings related to missing RBAC permissions (#2138).
• Captured WDT errors related to validating the model (#2140).
• Resolved an issue where the operator incorrectly missed Secrets or ConfigMaps in namespaces with a large number of either resource (#2199).
• Resolved an issue where the operator could report incorrect information about an introspection job that failed (#2201).
• Resolved an issue where a Service with the older naming pattern from operator 3.0.x could be stranded (#2208).
• Resolved an issue in the domain and cluster start scripts related to overrides at specific Managed Servers (#2222).
• The operator supports logging rotation and maximum file size configurations through Helm chart values (#2229).
• Resolved an issue supporting session replication when Istio is in use (#2242).
• Resolved an issue where the operator could swallow exceptions related to SSL negotiation failure (#2251).
• Resolved an issue where introspection would detect the wrong SSL port (#2256).
• Resolved an issue where introspection would fail if a referenced Secret or ConfigMap name was too long (#2257).

Operator 3.1.4

Resolved an issue where the operator would ignore live data that was older than cached data, such as following an etcd restore #2196.

Updated Kubernetes Java Client and Bouncy Castle dependencies.

Operator 3.1.3

Resolved an issue that caused some WebLogic Servers to fail to start in large Kubernetes clusters where Kubernetes watch notifications were not reliably delivered. #2188
Resolved an issue that caused the operator to ignore some namespaces it was configured to manage in Kubernetes clusters that had more than 500 namespaces. #2189

Operator 3.1.2

Resolved an issue where the operator failed to start servers in which the pods were configured to have an annotation containing a forward slash #2089.

Operator 3.1.1

This version resolves an issue that caused unexpected server restarts when the domain had multiple WebLogic clusters (#2109)