Releases: oracle/weblogic-kubernetes-operator
Releases · oracle/weblogic-kubernetes-operator
Operator 4.1.4
Other Changes
- The default WebLogic Monitoring Exporter version is now 2.1.8.
- Container image now uses Oracle Java SE 21 LTS
Bug Fixes
- Recreated container images following the October 2023 Oracle Linux Bulletin
- Resolved issue 4426 by adding tolerations to webhook deployment
Full Changelog: v4.1.3...v4.1.4
Operator 4.0.10
Other Changes
- The default WebLogic Monitoring Exporter version is now 2.1.8.
- Container image now uses Oracle Java SE 21 LTS
Bug Fixes
- Recreated container images following the October 2023 Oracle Linux Bulletin
Full Changelog: v4.0.9...v4.0.10
Operator 3.4.11
Other Changes
- The default WebLogic Monitoring Exporter version is now 2.1.8.
Bug Fixes
- Recreated container images following the October 2023 Oracle Linux Bulletin
Full Changelog: v3.4.10...v3.4.11
Operator 4.1.3
Bug Fixes
- Resolves issue #4368 by only applying volume mount overlap validation to the initialize domain on PV use case.
Full Changelog: v4.1.2...v4.1.3
Operator 4.1.2
Other Changes
- The default WebLogic Monitoring Exporter version is now 2.1.5.
- Added Domain and Cluster CRD support for topology spread constraints under the
serverPod
element.
Bug Fixes
- Corrected Doman and Cluster CRD usage of the IntOrString type.
Full Changelog: v4.1.1...v4.1.2
Operator 4.0.9
Other Changes
- The default WebLogic Monitoring Exporter version is now 2.1.5.
Bug Fixes
- Corrected Doman and Cluster CRD usage of the IntOrString type.
Full Changelog: v4.0.8...v4.0.9
Operator 3.4.10
Other Changes
- The default WebLogic Monitoring Exporter version is now 2.1.5.
Bug Fixes
- Corrected Doman and Cluster CRD usage of the IntOrString type.
Full Changelog: v3.4.9...v3.4.10
Operator 4.1.1
Major Changes
- The init container that sets the initial directory permissions prior to creating a domain on persistent volume will now default to running as a non-root user.
- Operator 4.1.0 added the ability to create a persistent volume (PV) and persistent volume claim (PVC) and then create the WebLogic domain home based on the provided WDT models.
- In the initial release of this feature, the init container would run as root. This has been changed and this container now runs as the same user, "oracle" (uid: 1000), that is used for the introspection and WebLogic Server instance containers.
- Customers can restore the original behavior with the new Domain resource field
initializeDomainOnPV.runDomainInitContainerAsRoot
.
- The
serverPod
field of the Domain and Cluster resources now supports standardenvFrom
content, allowing WebLogic Server instance containers to define environment variables that are sourced from a config map or secret. Variables that are defined in the values of these environment variables will not be replaced as they are for environment variables defined explicitly withenv
; however, any variables in theJAVA_OPTIONS
environment variable will be replaced if thespec.replaceVariablesInJavaOptions
field is set totrue
.
Other Changes
- Container image now uses Oracle Java SE 17 LTS
- Dependency updates for Okio and Bouncy Castle
Bug Fixes
- Liveness probe for WebLogic Server instance containers is hardened to fail whenever the server process is missing.
- Corrected processing of the
logHomeLayout
in thestartNodeManager.sh
script.
Full Changelog: v4.1.0...v4.1.1
Operator 4.0.8
Other Changes
- Container image now uses Oracle Java SE 17 LTS
- Dependency updates for Okio and Bouncy Castle
Bug Fixes
- Liveness probe for WebLogic Server instance containers is hardened to fail whenever the server process is missing.
- Corrected processing of the
logHomeLayout
in thestartNodeManager.sh
script.
Full Changelog: v4.0.7...v4.0.8