Digital.ai Deploy 23.1.x Release Notes
Digital.ai Deploy 23.1.0 includes the following new features:
- Migrate from Active/Hot-Standby Setup to Active/Active Setup
- Cache-enabled Deploy for better performance
- Tightly-coupled Deploy and Release for a seamless release orchestration and deployment experience
- Enhanced Pendo data collection for better troubleshooting
- Enhanced XL CLI
- Enhanced plugins
And more bug fixes and enhancements.
Support Policy
See Digital.ai Support Policy.
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 upgrade instructions, see:
Migrate from Active/Hot-Standby Setup to Active/Active Setup
Given the success of Active-Active setup with our customers, we have determined that the Deploy Active/Hot-standby mode is no longer the recommended configuration for achieving High Availability due to its inherent limitations. To ensure a more reliable and efficient solution, we strongly recommend migrating to the Active-Active setup.
Important: Plan and execute the migration from Deploy Active/Hot-standby to Active-Active before the designated deprecation date, which is the 1st of May, 2024.
To facilitate the transition, see the implementation details of the Active-Active setup. If you have any further questions or concerns regarding the Active-Active setup implementation, contact our Support team and your Customer Success Manager at Digital.ai.
After the deprecation date, support and updates for the Deploy Active/Hot-standby setup will not be available. Migrating to Active-Active is essential to maintain uninterrupted service and take advantage of the enhanced capabilities.
Note: We would like to take the opportunity to bring to your attention the Product and Support Lifecycle of Digital.ai Deploy. If you're using an unsupported version and need support with upgrading, contact your Customer Success Manager.
Cache-Enabled Deploy for Better Performance
-
Deploy 23.1 lets you cache frequently accessed data for better performance and reduced latency.
-
Caching is disabled by default, and you must enable it to start caching the data.
-
You can enable caching as part of Deploy installation or upgrade.
-
Digital.ai recommends Infinispan 14.0.2 for use with Deploy.
-
Digital.ai Deploy uses Cache-Aside (Lazy Loading) cache pattern to ensure that data is cached only when necessary and JCache (JSR-107) API as an abstraction over the cache.
Note: This feature is only available for Deploy on JVMs and Docker-based setups but not for Operator-based sites.
-
Comprehensive testing was carried out at Digital.ai to assess the effect of caching on the overall performance of the Digital.ai Deploy's deployment APIs.
-
A comparison of the performance test data from sites with and without caching was also carried out.
-
While the performance improvement was not that significant during initial deployments—as the cache was being built—we were able to witness significant performance improvements (by about 20-30 percentage as illustrated in the following table) during subsequent update deployments when the cache was fully built and utilized.
API Performance Improvement % /xldeploy/deployment/prepare/update
35% /xldeploy/deployment/prepare/deployeds
26% /xldeploy/deployment/validate
45% Total 33% For more information, see
-
You also have the following new actuator APIs to manage the cached data:
-
GET /actuator/jcaches
-
GET /actuator/jcaches/{cacheName}?key={key}
-
DELETE /actuator/jcaches/
-
DELETE /actuator/jcaches/{cacheName}
For more information, see Get and Delete Cached Data using API.
-
Tightly-coupled Deploy and Release
Digital.ai Deploy and Release 23.1 are more tightly-coupled than ever to bring you a seamless release orchestration and deployment experience.
- The new application onboarding workflows in Release makes it easier to seamlessly onboard deployed applications from Deploy and Argo CD without needing to work with the Deploy UIs or APIs.
- Once you onboard the applications, you can quickly discover which application versions are deployed to which environments across Deploy and Argo CD.
- Deploy's logs are now live-streamed to and visible in Release making it easier to identify and troubleshoot issues.
See Application Onboarding Overview for details.
Enhanced XL CLI
Here's a list of enhancements to the XL CLI 23.1.0:
- Added support for air-gapped installation of Deploy and Release.
- Added support for custom repositories in the install and upgrade wizards.
Known Issues
Some of the install wizard prompts are repeated (along with the user-entered value) when you run the install wizard via the xl kube install
command on Windows.
Version Upgrades—Supported Databases
Deploy 23.1 supports the following databases.
Database | Versions Supported |
---|---|
PostgreSQL | 14.6 and 15.0 |
MySQL | 5.7 and 8.0 |
Oracle | 19c |
Microsoft SQL Server | 2017 and 2019 |
DB2 | 11.1 and 11.5 |
Plugins and Integrations
Here's what's new and changed with plugins and integrations.
AWS Plugin
-
dded ability to deploy an AWS Lambda function from a container image.
-
hen you update a file from S3 bucket, the
FileName
error occurs. This issue is now fixed. -
dded options to
- create volumes at the time of instance creation
- enable encryption on volumes
-
dded new fields for metadata information that can enabled during instance creation.
Azure Plugin
-
Implemented AI.Deploy Azure plugin ACI with Azure Container Instances in the private registry (ACR). Two new fields, the Registry Username and Registry password are added.
-
dded ability to deploy an Azure functionApp from a container image.
-
ixed the file permission error caused while creating new
ResourceGroups
on Azure clusters. -
dded a check to ensure that rollback only deletes resource groups created using the arm template.
-
RequestDisallowedByPolicy
error is thrown when the Deploy Azure plugin is unable to communicate with Azure. This occurs because the policy at the client is set to allow only TLS 1.2. This issue is now fixed.
HashiCorp Vault Plugin
- nabled non-root token to be used for authentication with HashiCorp Vault.
Helm Plugin
- mplemented support for adding multiple repositories to Helm charts without downloading locally. Added the "Add Repository" checkbox to indicate if the repository must be added.
- dded a check for Namespace Field in Helm to fix installation issues.
JBoss Domain Plugin
- ixed an issue with the JBoss Domain plugin failing at the "Enable Data source" step.
OpenShift Plugin
- ndeploying a project deletes the project but the task continues to run in a loop, trying to complete the deletion. This issue is now fixed.
Terraform Plugin
- ixed an issue with the Terraform plugin deleting the .avsc file (Kafka schema) content during deployment.
Tomcat Plugin
- ixed an issue with the start, status, and stop control actions not working as expected with the Tomcat server on a remote host.
WebLogic Server Plugin
- ixed an issue with the rollback of Weblogic Side-by-Side application failing with
ItemAlreadyExistsException
exception.
WebSphere Application Server Plugin
- ixed an issue with the Create WAS Cluster feature not working.
- ixed an issue with the
rsplit
attribute missing in thestring
object.
Bug Fixes—23.1.16
- D-34534 - Fixed an issue with the Json patch dictionary CI in the
Environment
section that caused an error while manually executing a query during deployment.
Bug Fixes—23.1.15
None