1.5.0

Install instructions are here. For more information on using the Open Liberty Operator, see the new user guide.

Important: Are you upgrading from version 0.8.x or below? If so, before the upgrade, review the documentation on behavioural changes that could impact your applications.

Open Liberty Operator 1.5.0 includes the following features and changes:

Added

• Added support for collecting data for diagnosing performance-related problems using new custom resource OpenLibertyPerformanceData
• Added support for memory and custom metrics-based autoscaling (.spec.autoscaling)
• Support for optional pull secrets in custom service accounts is added (.spec.serviceAccount.skipPullSecretValidation)

Changed

• Changed the output location of OpenLibertyTrace operation to subfolder logs within the serviceability directory for the pod (i.e. /serviceability/my_namespace/my_pod_name/logs). Upon successfully enabling tracing, the field .status.logDirectory will include the location of the logs directory that will include the server logs and traces.
• Changed the output location of OpenLibertyDump operation to subfolder serverDumps within the serviceability directory for the pod (i.e. /serviceability/my_namespace/my_pod_name/logs/serverDumps). Upon successful completion of the dump operation, the field .status.dumpFile will include the location of the dump file.
• Changed the output location of java dumps (javacore, heap dump, core dump, etc), when serviceability storage (.spec.serviceability) is enabled, from /serviceability to the subfolder logs within the serviceability directory for the relevant pod (i.e. /serviceability/my_namespace/my_pod_name/logs). Liberty environment variables LOG_DIR, IBM_HEAPDUMPDIR, IBM_COREDIR and IBM_JAVACOREDIR are also set to the same logs subdirectory.
• Changed the base image of Operator and catalog source to UBI 9 Minimal.
• Updated the Operator SDK, Kubernetes, Go libraries, APIs and operating system packages to include security fixes.