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!

Operator 2.0 release candidate 1

Operator is now installed via Helm charts, replacing the earlier scripts. The operator now supports domain home on persistent volume or in Docker image use cases, which required a redesign of the Domain schema. Customers can override domain configuration using configuration override templates. Load balancers and Ingress can now be independently configured. WebLogic logs can be directed to a persistent volume or WebLogic server console out can be directed to the pod log. Added lifecycle support for servers and significantly more configurability for generated pods. The final v2.0 release will be initial release where the operator team intends to provide backward compatability as part of future releases.

Release version 1.1

This is a minor, bug-fix release. The following changes are included:

• Improvements to documentation that describe how to scale a WebLogic cluster.
• Add documentation to list steps needed to restart domain when changes have been made to the domain properties.
• Operator resumes processing after Domain resource deleted and recreated.
• Corrected WebLogic cluster instability when startupControl is set to "ALL".
• Expose server name via javaOptions.
• Update Java Kubernetes client to 2.0.0.
• Add validation for Apache loadBalancerVolumePath.
• Upgrade Jackson databinding version to 2.9.6.
• Create headless Services per WebLogic server instance.
• Reduce number of warning messages when reading WebLogic domain configuration.
• Resolve memory continuously growing by preventing the request parameters list from growing indefinitely.
• Document recommendation to use NFS version 3.0 for running WebLogic Server on OCI Container Engine for Kubernetes.
• Add validation of legal DNS names for domainUID, adminServerName, managedServerNameBase, and clusterName.