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.

Operator 2.4.0

Includes fixes for a variety of issues related to FMW infrastructure domains and pod variable substitution. The operator now uses WebLogic Deploy Tooling 1.6.0 and the latest version of the Kubernetes Java Client.

Operator 2.3.0

This release adds support for Coherence cluster rolling, pod templating and additional pod content, and experimental support for running under an Istio service mesh.

Operator 2.2.1

The operator now supports Kubernetes 1.14.0+.

This release is primarily a bug fix release and resolves the following issues:

• Servers in domains, where the domain home is on a persistent volume, would sometimes fail to start. These failures would be during the introspection phase following a full domain shutdown. Now, the introspection script better handles the relevant error conditions.

• The domain resource provides an option to pre-create Kubernetes services for WebLogic Servers that are not yet running so that the DNS addresses of these services are resolvable. These services are now created as non-headless so that they have an IP address.

Operator 2.2.0

New features and fixes in this release:

Added support for FMW Infrastructure domains.
WebLogic Server instances are now gracefully shut down by default and shutdown options are configurable.
Operator is now built and runs on JDK 11.