Operator 3.1.1

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

Operator 3.0.4

This release contains a back-ported fix from 3.1.0 for Managed Server pods that do not properly restart following a rolling activity.

Operator 3.1.0

• All fixes included in 3.0.1, 3.0.2, and 3.0.3 are included in 3.1.0.
• Sample scripts to start and stop server instances #2002
• Support running with OpenShift restrictive SCC #2007
• Updated default resource and Java options #1775
• Introspection failures are logged to the operator's log #1787
• Mirror introspector log to a rotating file in the log home #1827
• Reflect introspector status to domain status #1832
• Ensure operator detects pod state changes even when watch events are not delivered #1811
• Support configurable WDT model home #1828
• Namespace management enhancements #1860
• Limit concurrent pod shut down while scaling down a cluster #1892
• List continuation and watch bookmark support #1881
• Fix scaling script when used with dedicated namespace mode #1921
• Fix token substitution for mount paths #1911
• Validate existence of service accounts during Helm chart processing #1939
• Use Kubernetes Java Client 10.0.0 #1937
• Better validation and guidance when using longer domainUID values #1979
• Update pods with label for introspection version #2012
• Fix validation error during inrtrospector for certain static clusters #2014
• Correct issue in wl-pod-wait.sh sample script #2018
• Correct processing of ALWAYS serverStartPolicy #2020

Operator 3.0.3

This release contains a fix for pods that are stuck in the Terminating state after an unexpected shut down of a worker node.

Operator 3.0.2

This release contains several fixes, including improvements to log rotation and a fix that avoids unnecessarily updating the domain status.

Change log:

• Removed unnecessary duplicated parameter in initialize-internal-operator-identity.sh script #1867
• Support nodeAffinity and nodeSelector for the operator in its Helm chart #1869
• Log file rotation enhancements and documentation #1872 #1827
• Production support for the NGINX ingress controller #1878
• Prevent unnecessary changes to Domain status that were causing churn to the resourceVersion #1879
• Better reflect introspector status in the Domain status #1832
• Create each pod after any previous pods have been scheduled to allow for correct anti-affinity behavior #1855

Operator 3.0.1

Fixed an issue preventing the REST interface from working after a Helm upgrade. Helm 3.1.3+ now required.

Operator 3.0.0

Adds Model in Image feature and support for applying topology and configuration override changes without downtime. Removal of support for Helm 2.x. Operator performance improvements to manage many domains in the same Kubernetes cluster.

Operator 2.6.0

Kubernetes 1.16, 1.17, and 1.18 support. Removal of support for Kubernetes 1.13 and earlier. This release can be run in the same cluster with operators of either 2.5.0 and below, or with 3.x providing an upgrade path. Certified support of Oracle Linux Cloud Native Environment (OLCNE) 1.1 with Kubernetes 1.17.0.

Operator 3.0.0 Release Candidate 1

Adds Model in Image feature. Support for Kubernetes 1.16. Removal of support for Kubernetes 1.13 and earlier. Removal of support for Helm 2.x. This release candidate cannot be run in the same cluster as another release of the operator. You can upgrade from 2.5.0 to 3.0.0-rc1 without needing to restart or recreate any existing domains. However, please note that we do plan to support running the final 3.0.0 release in the same cluster with at least one 2.x release of the operator to allow for staged migration.

Operator 2.5.0

Support for Helm 3.x and OpenShift 4.3. Operator can be installed in a namespace-dedicated mode where operator requires no cluster-level Kubernetes privileges. This version is not supported on Kubernetes 1.16+, check the prerequisites.