Upgrade instructions

The Digital.ai Deploy upgrade process you use depends on the version from which you are upgrading, and the version to which you want to go.

For detailed instructions based on your upgrade scenario, refer to Upgrade Deploy.

Digital.ai Deploy 22.0 has a support term of 12 months from the date of release. For more information, see Digital.ai Support Policy.

Digital.ai Deploy 22.0.0

In addition to bug fixes, the Digital.ai Deploy 22.0.0 includes the following new features:

• Separate server distribution to install the Deploy worker
• Kubernetes Operator Enhancements
• Updates to the following Deploy plugins
  • Google Cloud Kubernetes plugin
  • Helm plugin

Separate Server Distribution to Install the Deploy Worker

With Deploy 22.0, you can install the worker on a separate server—using the new Deploy Task Engine installer. The new Deploy Task Engine installer is an abridged version of the Deploy installer that has the bare essentials required to install and run Deploy Workers on a separate server. This means that the Deploy Task Engine has just the code related to execution of tasks, which reduces the load on the server. For more information, see linkTBD.

Kubernetes Operator Enhancements

With Deploy 22.0, the Kubernetes Operator-based installer offers the following enhancements:

• Kubernetes Operator supports installation of Digital.ai Deploy on Google Cloud Platform (GCP)
• You can migrate to Deploy 22.0 from Deploy 10.2 on the following platforms:
  • Amazon EKS
  • Azure Kubernetes Service (AKS)
  • Kubernetes On-premise
  • OpenShift cluster on Amazon EKS
  • OpenShift cluster on VMWare vSphere
  • Google Cloud Platform (GCP)
• From Deploy 22.0, KeyCloak is the default authentication provider for Deploy

For more information, see linkTBD.

Plugins and Integrations

• Google Cloud Kubernetes Plugin

  • The x509 certificate-based authentication has been deprecated. Deploy 22.0 brings you token-based authentication for Google Cloud Kubernetes (GKE). You can now use token-based authentication with Google Cloud Kubernetes (GKE).
  • You can now use Amazon EKS and Azure AKS service accounts when you want to log on to (access resources) Amazon EKS and Azure AKS Kubernetes clusters using Deploy's Kubernetes plugin.

• Helm Plugin Fixed an issue that caused incorrect exceptions (warnings) during helm chart deployment and un-deployment using the UseClusterConfiguration feature.

Bug fixes

Bug fixes—10.3.2

• [ENG-1998] - Modified the Deployment Mapping screen message.
• [ENG-2022] - Fix made to ensure multiple updates to the same CI will pick the latest key and token from the previous update for WAS Plugin.
• [ENG-4296] - Fixed the deployment packages sorting issue.
• [ENG-6934] - Fixed the Force Redeploy issue that breaks the deployment rollback feature.
• [ENG-8081] - Fixed the Worker Retry Connection failure issue.
• [ENG-7400] - Fixed the "Failed to Deserialize Payload" error in Deploy 10.3 GUI.
• [ENG-7800] - Fixed the deployment issue in Deploy 10.2.4.
• [ENG-7980] - Fixed the broken Jython patch for issues 2618 and 2894.
• [FI-744] - Fixed the issue where XL-deploy failed when configured to start the JMX.
• [FI-798] - Fixed the issue where the upgrade to 10.2.2 Directory reference updates cannot be applied.
• [FI-800] - Fixed the placeholders issue where the empty folders are deleted.
• [FI-813] - Fixed the Deploy application unresponsiveness caused by session timeout.
• [FI-829] - Fixed the "Cannot be cast error" when upgrading XLD from 9.5.3 to 10.2.2.