Releases: oracle/weblogic-kubernetes-operator
Releases · oracle/weblogic-kubernetes-operator
Operator 3.4.8
Other Changes
- Container image now uses Oracle Java SE 17 LTS
Bug Fixes
- Liveness probe for WebLogic Server instance containers is hardened to fail whenever the server process is missing.
- Removed Helm chart usage of built-in Kubernetes roles system:auth-delegator and system:discovery.
- Corrected Helm chart generation of
javaLoggingFileSizeLimit
. - Corrected domain and cluster CRD generation of quantity-typed fields, such as
emptyDir.sizeLimit
. - Resolved an issue related to
seccompProfile
security context entry on OpenShift.
Full Changelog: v3.4.7...v3.4.8
Operator 4.1.0
Deprecation Notices
- Model in Image without auxiliary images (the WDT model and installation files are included in the same image with the WebLogic Server installation) is deprecated in WebLogic Kubernetes Operator version 4.0.7. Oracle recommends that you use Model in Image with auxiliary images.
Additional Features
- Support for the automated creation of domains on persisted volumes where the initial domain topology and resources are described using WebLogic Deploy Tooling (WDT) models.
Bug Fixes
- All bug fixes included in the 4.0.7 release are also included in this release.
Full Changelog: v4.0.7...v4.1.0
Operator 4.0.7
Deprecation Notices
- Model in Image without auxiliary images (the WDT model and installation files are included in the same image with the WebLogic Server installation) is deprecated in WebLogic Kubernetes Operator version 4.0.7. Oracle recommends that you use Model in Image with auxiliary images.
Other Changes
- The Helm chart now supports the
jvmOptions
value that specifies the Java options used to run the operator process and the default value includes a reasonable value for-XXMaxRAMPercentage
. - The default WebLogic Monitoring Exporter version is now 2.1.4.
Bug Fixes
- Removed Helm chart usage of built-in Kubernetes roles system:auth-delegator and system:discovery.
- Corrected Helm chart generation of
javaLoggingFileSizeLimit
. - Corrected domain and cluster CRD generation of quantity-typed fields, such as
emptyDir.sizeLimit
. - Samples now generate valid cluster resources when the WebLogic cluster name includes characters that are not permitted in resource names.
- The operator now correctly deletes external services when no longer required.
- The introspection job generated by the operator is no longer excluded from the Istio Mesh.
- When the operator cannot validate the contents of the domain and cluster CRDs, such as in dedicated mode use cases where the operator does not have cluster-level privileges, the number of warning messages in the operator's log is limited.
Full Changelog: v4.0.6...v4.0.7
Operator 4.0.6
- Resolved several issues related to delayed watch notifications:
- Resolved an issue where an introspection Failed domain status message is generated.
- Resolved an issue where a DOMAIN_CHANGED event was not generated.
- Resolved an issue where a Cluster was marked as Failed.
- Resolved an issue where the WDT model has a Server named "adminserver", but does not explicitly specify that this server is the Administration Server using the AdminServerName.
- Update the SnakeYAML dependency to version 2.0.
- Added support for new zip structure in WDT archive for database wallets.
- Container image is now multi-platform, including support for AMD64 and ARM64.
- Resolved an issue where the operator would generate invalid URLs for WebLogic Server instances if the namespace name started with a numeric character.
- Resolved an upgrade issue related to security contexts on init containers.
- Resolved an issue related to
seccompProfile
security context entry on OpenShift.
Operator 3.4.7
- Resolved an issue related to WDT models that do not contain AdminServerName.
- Updated usage of the SnakeYAML SafeConstructor to avoid usage of the empty-arguments constructor.
Operator 4.0.5
- Updated the Fluentd integration to make the Elasticsearch credentials optional and to allow the specification of the container command and arguments.
- Resolved an issue related to growth in the number of WebLogic sessions related to the monitoring exporter and health checks.
- Resolved issue #3865 related to decorating the name of the ConfigMap for Fluentd integration (#3883).
- Updated the generation of pods and containers for security best practices.
- Added support to specify the container resources and Java options for the introspector job.
- Changed the Helm chart to disable the operator's REST endpoint by default. This endpoint is only needed for WLDF action based scaling. All other forms of scaling are unaffected by this change.
- Resolved an issue related to schema webhook conversion of the
domainHomeInImage
field. - Resolved an issue related to schema webhook conversion of status conditions only supported for "v9" schema.
- Resolved an issue related to the ordering of init containers generated for "v8" style auxiliary images.
- Resolved several issues related to the generation of Domain and Cluster deletion events.
- Resolved an issue related to using the
nodeSelector
andaffinity
values with the operator's Helm chart. - Resolved several issues related to WebLogic Deploy Tooling (WDT) models for Model in Image.
- Added support or provided clearer validation errors for cases where
AdminServerName
is set or missing and where there is or is not a matching entry underServer
. - Improved support for dynamic clusters that do not specify
ServerTemplate
orDynamicClusterSize
. - Provided clearer validation errors for dynamic clusters that have no member servers defined under
DynamicServers
.
- Added support or provided clearer validation errors for cases where
- Resolved an issue related to a StringIndexOutOfBoundsException generated while ensuring container port names are not longer than the Kubernetes enforced maximum of 15 characters.
- Updated the default WebLogic Monitoring Exporter injection to version 2.1.2.
Operator 3.4.6
- Resolved several issues related to WebLogic Deploy Tooling (WDT) models for Model in Image.
- Added support or provided clearer validation errors for cases where
AdminServerName
is set or missing and where there is or is not a matching entry underServer
. - Improved support for dynamic clusters that do not specify
ServerTemplate
orDynamicClusterSize
. - Provided clearer validation errors for dynamic clusters that have no member servers defined under
DynamicServers
.
- Added support or provided clearer validation errors for cases where
- Resolved an issue related to a StringIndexOutOfBoundsException generated while ensuring container port names are not longer than the Kubernetes enforced maximum of 15 characters.
- Updated the default WebLogic Monitoring Exporter injection to version 2.1.2.
Operator 3.4.5
- Resolved issue #3865 related to decorating the name of the ConfigMap for Fluentd integration (#3883).
- Updated the default WebLogic Monitoring Exporter injection to version 2.1.1.
- Updated several dependencies, including Jackson Databind to version 2.14.1 and the Oracle Linux base for the container image to version 9.
Operator 4.0.4
- Resolved an issue related to the
logHomeLayout
field during schema conversion from "v8" to "v9" Domains.- Operator 4.0 introduced the
logHomeLayout
field to control the organization of WebLogic Server instance log files. - The default value for
logHomeLayout
isByServers
; however, the operator 3.4 behavior was consistent with the value ofFlat
. - Therefore, schema conversion from "v8" to "v9" Domains now explicitly selects a
logHomeLayout
value ofFlat
.
- Operator 4.0 introduced the
- Resolved an issue during uninstall where the validating webhook was leaving behind a ValidatingWebhookConfiguration resource. This resource is now deleted.
Operator 4.0.3
- The Helm chart now excludes the operator's webhook from running in an Istio mesh.
- Communication from the operator to WebLogic Server instances or to the WebLogic Monitoring Exporter sidecar use the service name and namespace rather than IP addresses to be more compatible with Istio strict mutual TLS mode.
- Resolved an issue where the
Completed
status condition would be set to true too early during the scale down of a cluster to 0 replicas. - The Model in Image sample now uses "v9" style auxiliary images.
- The coordination between the periodic listing of Domain and Cluster resources and the processing of watch notifications has been improved to increase operator efficiency.