Skip to content

Latest commit

 

History

History
33 lines (26 loc) · 1.98 KB

recent-changes.md

File metadata and controls

33 lines (26 loc) · 1.98 KB
Raw

Recent changes to the Oracle WebLogic Server Kubernetes Operator

This document tracks recent changes to the operator, especially ones that introduce backward incompatibilities.

Release 1.1

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

Release 1.0

Changes:
  • Added support for dynamic clusters.
  • Added support for Apache HTTP Server, the Voyager Ingress Controller.
  • Added support for PV in NFS storage for multi-node environments.

Release 0.2

Changes:
  • Several files and input parameters have been renamed. This affects how operators and domains are created. It also changes generated Kubernetes artifacts, therefore customers must recreate their operators and domains. Introduces Backward Incompatibility
  • Many Kubernetes artifact names and labels have changed. Also, the names of generated YAML files for creating a domain's PV and PVC have changed. Because of these changes, customers must recreate their operators and domains. Introduces Backward Incompatibility