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.

Operator 2.1

Features and issues fixed in this release:

Customers can configure init and sidecar containers for generated pods for server instances
Services are now consistently cleaned-up on scale down or when fully stopping a domain
Resolved a timing issue between domain status updates and scaling actions

Operator 2.0.1

Features and issues fixed in this release:

Certified for use on OpenShift.
Fixed readiness probe initial period (was too short and could cause pods to be killed prematurely) and fixed readiness probe address (would not work with load balancers).
Helm archive is available so that the operator can be installed without cloning this repository.
Upgraded samples to use logstash:6.6.0.
Issue #726: Channel ports are now generated for clustered services.
Container ports are now fully populated for the Administration Server.
Operator's REST endpoint private key is now specified using a Kubernetes secret.
Several fixes for configuration override processing.

Operator 2.0

General availability version of Operator 2.0.

Operator 2.0 release candidate 2

Schema for the 2.0 domain custom resource is now final.

Please be aware that domains created with 2.0 release candidate 1 are not compatible with release candidate 2. You will need to delete any preexisting domains from release candidate 1 and regenerate their domain.yaml files.

Many other bug fixes found by our early access testers have been fixed. Thanks for your support!