WebLogic Kubernetes Toolkit UI v1.7.0

Major New Features

None

Other Changes

• #294 - Updated application to be compatible with WebLogic Deploy Tooling 4.x.

Bug Fixes

None

Known Issues

• On Mac, the embedded version of WDT 4.1.0 does not include the jansi-2.4.1 JAR file that WDT's interactive Model Help tool requires due to an Apple requirement to sign the native code inside this third-party JAR file. User's can either install their own version of WDT or copy the jar file from another install if they really need to use it from the embedded location.
• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multicluster installation.
• Verrazzano Application components Ingress Trait Rules table's URL column does not properly account for multicluster
  applications. The Update URL button will only get information from the admin (i.e., local) cluster.

WebLogic Kubernetes Toolkit UI v1.6.3

Major New Features

None

Other Changes

• #293 - Updated Model Design View to use WebLogic Remote Console 2.4.8

Bug Fixes

None

Known Issues

• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multicluster installation.
• Verrazzano Application components Ingress Trait Rules table's URL column does not properly account for multicluster
  applications. The Update URL button will only get information from the admin (i.e., local) cluster.

WebLogic Kubernetes Toolkit UI v1.6.2

Major New Features

None

Other Changes

• #287 - Added support for WebLogic Kubernetes Operator domain specification's precreateService setting.

Bug Fixes

• #286 - Fixed an issue related to SSL termination and pass through Ingress resource generation.

Known Issues

• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multicluster installation.
• Verrazzano Application components Ingress Trait Rules table's URL column does not properly account for multicluster
  applications. The Update URL button will only get information from the admin (i.e., local) cluster.

WebLogic Kubernetes Toolkit UI v1.6.1

Major New Features

None

Other Changes

None

Bug Fixes

• #281 - Fixed issue with Ingress Controller shell script not using elif.
• #282 - Fixed issue with busy dialog referencing "auxiliary image" while building a domain creation image.
• #283 - Fixed a typo in the Verrazzano application page in its reference to the Manual Scaler trait.
• #285 - Fixed issues with the Domain shell script when using JRF domains on a persistent volume.

Known Issues

• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multicluster installation.
• Verrazzano Application components Ingress Trait Rules table's URL column does not properly account for multicluster
  applications. The Update URL button will only get information from the admin (i.e., local) cluster.

WebLogic Kubernetes Toolkit UI v1.6.0

This release has major usability changes to clearly delineate the following use cases:

• A project that contains a WDT model
• A project that does not have a model but uses an "external image" that contains a model
• A project with no model

When actions are not relevant to the use case, action buttons and Go menu items are hidden. When the project does
not contain a model, the Model page is disabled. When the project is using an external image that contains a model,
the user is allowed to specify the clusters, variable overrides, and secrets from this external model.

Major New Features

None

Other Changes

• #250 - Changed domain spec default auxiliary image locations to align with those on the image page. This allows
  the user to switch back-and-forth between creating and using an auxiliary image without modifying location
  field values.
• #251 - Added Inspect Image button to allow users to locate the WDT Model and Install Home locations in an external image.
• #253 - Added support for SAML2 Data Initialization files to the Model Archive Editor.
• #254, #255, #256, #258, #260, #265, #267 - Added support for WebLogic Kubernetes Operator 4.1.0 domain creation images.
• #257 - Changed the action buttons and Go menu items to dynamically show/hide themselves based on the use case selected.
• #259 - Added the ability to set domain-wide environment variables in the WebLogic Kubernetes Operator domain spec.
• #268 - Reorganized the Secrets table to better support any extra secrets required by the model.
• #270 - Added a warning for Verrazzano users using OKE Native Pod Networking.
• #280 - Enhanced the Verrazzano Application page's Add Components dialog to allow multiple components to be selected at a time.

Bug Fixes

• #261 - Fixed a bug with the Model Archive Editor that was preventing adding name-segregated entries from working correctly.
• #262 - Fixed a bug related to getting the WebLogic Kubernetes Operator version when the logs were too large.
• #264 - Fixed a bug that caused the Verrazzano installation to use the wrong Verrazzano Platform Operator URL in some cases.
• #276 - Fixed a bug where the WebLogic Kubernetes Operator cluster resources were created after the domain resource, which
  resulted in a temporary error condition when the operator analyzed the domain. This fix results in the Code View
  showing the cluster resources before the domain resource.
• #277 - Added a missing tooltip to the Verrazzano Application component's Ingress Trait Rules table Update URLs button
  to clarify that it should only be used after the application status is complete.
• #279 - Fixed a bug that was causing the title of the Update URLs error dialog box to display the i18n key instead of the text.

Known Issues

• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multicluster installation.
• Verrazzano Application components Ingress Trait Rules table's URL column does not properly account for multicluster
  applications. The Update URL button will only get information from the admin (i.e., local) cluster.

WebLogic Kubernetes Toolkit UI v1.5.3

Major New Features

None

Other Changes

• #242 - Added initial (very minimal) internationalization support bundles.
• #245 - Added an Ingress Controller Service Type field that can be used when installing an ingress controller to
  a Kubernetes cluster without a load balancer.

Bug Fixes

• #241 - Fixed a bug with the WebLogic Image Tool's --wdtHome argument when it ended with weblogic-deploy.
• #246 - Worked around a WebLogic Kubernetes Operator issue where the javaLoggingFileSizeLimit value was not working
  due to Helm issue 1707.
• #247 - Fixed issue with Open Project when storing the credentials in the project and entering the wrong passphrase
  that was causing the UI to not allow re-opening the project.

Known Issues

• In the Model Design View when creating an App Deployment or Shared Library, changing the Source field back to an empty value
  results in a bogus error message about not removing the deployment from the archive file. This error is harmless so simply
  dismiss the error dialog and continue.
• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multicluster installation.

WebLogic Kubernetes Toolkit UI v1.5.2

Major New Features

None

Other Changes

None

Bug Fixes

• #232 - Fixed an issue in the Verrazzano Application page where the component's Ingress Trait Rule destination names
  were not properly converted to legal Kubernetes names so that they would match the generated service names when the
  domain, cluster, or server names combinations had more than one disallowed characters in them.

Known Issues

• In the Model Design View, changing the Source Path and Plan Path fields for existing App Deployments and Shared Libraries
  is broken in this release. To work around it, either remove and recreate the deployment or use the Model Code View's
  Model Editor and Archive Editor to make the appropriate changes.
• In Model Design View, the Plan/Plan Path fields for App Deployments mistakenly allow you to select a directory. This is
  not valid and will result in an error. Please make sure to select a file for any deployment plan.
• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multi-cluster installation.

WebLogic Kubernetes Toolkit UI v1.5.1

Major New Features

None

Other Changes

None

Bug Fixes

• #229 - Fixed issue in Domain resource generation on Windows inserting a path with Windows separators

Known Issues

• In the Model Design View, changing the Source Path and Plan Path fields for existing App Deployments and Shared Libraries
  is broken in this release. To work around it, either remove and recreate the deployment or use the Model Code View's
  Model Editor and Archive Editor to make the appropriate changes.
• In Model Design View, the Plan/Plan Path fields for App Deployments mistakenly allow you to select a directory. This is
  not valid and will result in an error. Please make sure to select a file for any deployment plan.
• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multi-cluster installation.

WebLogic Kubernetes Toolkit UI v1.5.0

Major New Features

None

Other Changes

• #202 - Added support for Verrazzano 1.5.0+ (which uses WebLogic Kubernetes Operator 4.0.0+).
• #204 - Updated the Archive Editor to align with WebLogic Deploy Tooling 3.0.0+ changes to the archive format.
• #205 - Added support for installing the optional Verrazzano component Argo CD with Verrazzano 1.5.0+.
• #205 - Added support to configure Kubernetes connectivity data for Verrazzano managed clusters.
• #210 - Added support for Verrazzano Get Application Status action to check the status on the correct cluster using a
  multi-cluster application targeted to one or more managed clusters.
• #213 - Improved Verrazzano Ingress Trait rule editor to allow the user to choose the Destination Host by WebLogic cluster or non-clustered server name.
• #215 - Added a Update URLs button to the Verrazzano application's Ingress Trait that populates the Ingress Rules table
  with a URL once the application deployment is complete.
• #221 - Streamlined the WKO Ingress Routes table to conserve space.
• #223 - Added Proxy URL validation to the network connection and User Preferences dialogs to make sure the user enters
  a URL and not just a host:port combination.

Bug Fixes

• #201 - Fixed a bug where the project file was not being cleaned up properly when a cluster was removed and Prepare Model was run again.
• #205 - Fixed a bug that caused the Verrazzano Get Application Status call to fail.
• #211 - Fixed a bug with sorting the Ingress Rule's Route Annotations table's columns.
• #214 - Fixed a bug where the Verrazzano Check Verrazzano Install Status action was reporting installation is still in progress after a successful upgrade.
• #216 - Improved the behavior of the Model Code View sliders when the window is resized.
• #217 - Fixed a bug where the kubectl version output was reporting an incorrect server version number with newer versions of Kubernetes.
• #219 - Fixed a bug with Verrazzano 1.4.0+ installation where the wrong Verrazzano Platform Operator file name was being used.
• #220 - Cleaned up the table formatting/behavior across the application.
• #222 - Fixed a bug with container image tag validation that was causing regular expression catastrophic backtracking, leading to slow validation responses.

Known Issues

• In the Model Design View, changing the Source Path and Plan Path fields for existing App Deployments and Shared Libraries
  is broken in this release. To work around it, either remove and recreate the deployment or use the Model Code View's
  Model Editor and Archive Editor to make the appropriate changes.
• In Model Design View, the Plan/Plan Path fields for App Deployments mistakenly allow you to select a directory. This is
  not valid and will result in an error. Please make sure to select a file for any deployment plan.
• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Get Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• Verrazzano installation does not support a multi-cluster installation.

WebLogic Kubernetes Toolkit UI v1.4.1

Major New Features

None

Other Changes

• #192: Add the ability to install and work with older versions of operator using the latest published Helm chart.

Bug Fixes

• Resolved issue Discover Model issue introduced in 1.4.0 by picking up the fix in WebLogic Deploy Tooling 2.4.1.
• Resolved issue with Deploy Domain failing due to a WebLogic Kubernetes Operator error from the new conversion/validating
  webhook (fix in a new published version of the WebLogic Kubernetes Operator 4.0.0 Helm chart).
• #190: Resolved a macOS-specific issue in check to see if the WebLogic Kubernetes Operator is already installed.
• #191: Resolved WebLogic Kubernetes Operator 4.0 issues with the Domain Resource spec generation.
• #191: Resolved an issue with WebLogic Kubernetes Operator 3.x where the wdtInstallHome was named incorrectly under one condition.
• #191: Resolved a gap in the functionality for WDT and Model locations in the Domain Resource spec when using images
  instead of creating them.

Known Issues

• On Linux, the open and save dialogs open behind the main application window. This is due to
  Electron bug 32857.
• When deploying a Verrazzano application, the Check Application Status button only checks the status of the project's
  Verrazzano component containing the WebLogic domain specification.
• WKTUI does not currently show the Verrazzano URL needed to access the application. The URL will always be of
  the form https://<gateway-hostname>/<app-path>, where the gateway-hostname is the name created by Verrazzano
  in the Gateway object. To get the name of the generated gateway object, run kubectl get gateway -n <namespace> --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}'. Next, run kubectl get gateway <gateway-name> -n <namespace> -o yaml
  and review the hosts entry of the .spec.servers section to find the DNS name that corresponds to the
  gateway-hostname to use in the URL.