Release Date US: 2023/12/20
Release Date AU/EU: 2023/12/21
This release provides standard maintenance updates - delivering performance, security, and reliability improvements in these areas:
- Longhorn migrated to OpenEBS
- Docker migrated to containerd
- Weave migrated to Flannel
- Resolves errors in horizontal scaling
- Improves search service memory management
- Additional installation improvements
Please Pay Attention to the Important Considerations in the User Guide!
Upgrading Jama Connect to 8.79.6, 9.0.4, or 9.6.x requires that you first update the Jama Connect KOTS platform (please refer to page 480 on the v9.6.x User Guide). The updated KOTS platform optimizes how data is stored in Jama Connect and how KOTS resources communicate with one another.
IMPORTANT
Upgrading your current environment involves significant maintenance downtime and requires that you have a recovery plan in case you need to revert to the original environment. Instead, we recommend that you install a new Jama Connect environment (referred to as a clean installation), then copy elements of your current environment to the new environment.
Here are the supported upgrade scenarios:
-
(Recommended) Clean installation of Jama Connect KOTS
- This recommended scenario requires that you install a clean Jama Connect KOTS instance on a new application server, then copy data assets and the tenant.properties file from your current environment to the new environment.
- The new instance must point to a restored backup of your database.
- The new instance must point to a restored backup of your database.
- This recommended scenario requires that you install a clean Jama Connect KOTS instance on a new application server, then copy data assets and the tenant.properties file from your current environment to the new environment.
-
In-Place Upgrade of Jama Connect KOTS
- This scenario requires upgrading your current environment in place, which involves significant maintenance downtime and requires that you have a recovery plan in case you need to revert to the original version.
- You must run a pre-upgrade script before running the Kubernetes (kURL) installer.
- You must run a pre-upgrade script before running the Kubernetes (kURL) installer.
- This scenario requires upgrading your current environment in place, which involves significant maintenance downtime and requires that you have a recovery plan in case you need to revert to the original version.
Resolved Issue
ID | Description |
SOS-DEF-7091 | In airgap installations container images are no longer removed during the installation process, which no longer requires a manual workaround. |
Related to
Comments
0 comments
Please sign in to leave a comment.