Applies to:
Kyvos Enterprise Kyvos Cloud (SaaS on AWS) 
Kyvos AWS Marketplace
Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)
...
This section provides information to upgrade and rollback Kyvos Manager.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note
|
...
Log in to Kyvos Manager machine through the terminal.
Navigate to the Kyvos Manager installation path.
Stop the Kyvos Manager process using the command:
./kyvosmanager/bin/stop-km.shIdentify the location for the used kyvosmanagerdata folder. For this, check the value of KM_DATA_DIR in the set env.sh file in the bin folder.
This folder contains the Kyvos Manager data including the repository.Go to parent folder of the kyvosmanagerdata folder and run the command.
tar -zcvf file_name.tar.gz kyvosmanagerdata
Here file_name is the user backup file name for the Kyvos Manager.Copy the backup file to the local machine.
Rename your current repo folder at the kyvosmanagerdata/server location, such as repo_<oldversion number>. For example, you can name it repo_2020.5.
Upgrade Kyvos Manager and Kyvos
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
You can easily upgrade both Kyvos and Kyvos Manager applications to a newer version by simply selecting the required version from the Kyvos Manager portal.
From Kyvos 2024.3 onwards, this This is applicable to all environments.
Int he In the table below:
MP = Marketplace | MS = Managed Services | SNS = Single Node Standard | Ent = Enterprise
| AWS | AWS MP | AWS MP SNS | Azure MP | Azure MP SNS | GCP MP | GCP MP SNS | AWS Ent | Azure Ent | GCP Ent | On-Premise |
Single Click Upgrade | |
|
| | | |
| |
|
|
|
Single Click Rollback | | | | | | | | |
|
|
|
Independent Kyvos Patch (Version Dropdown / text input based) |
| |
|
|
| | |
|
|
|
|
Independent Kyvos Patch |
|
|
|
|
|
|
|
|
|
|
|
Independent Kyvos Upgrade (upload / list) |
|
|
|
|
|
|
|
|
|
|
|
Independent Kyvos Rollback |
|
|
|
|
|
|
|
|
|
|
|
Independent KM Upgrade (upload / list) |
|
|
|
|
|
|
|
|
|
|
|
Independent KM Rollback |
|
|
|
|
|
|
|
|
|
|
|
...
| panelIconId | atlassian-note |
|---|---|
| panelIcon | :note: |
| bgColor | #DEEBFF |
Note
...
On the navigation pane, click Application Update > Upgrade.
On the Upgrade Kyvos Manager page, provide the information as:
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note Kyvos Manager Tomcat Server logs will be generated in the kyvosmanagerdata/server/tomcatLogs location even after upgrading the Kyvos Manager version. |
Upgrade Kyvos Manager in Azure
...
Switching to the previous version of Zookeeper
To access the previous version of the Zookeeper, perform the following steps.
Add the previous Zookeeper version bundle to the Kyvos Manager repository at kyvosmanagerdata/server/repo/ .
Take a backup of the new version 3.7.1 bundle of Zookeeper at a different location outside the Kyvos Manager repo. This bundle will be necessary for switching to the new version 3.7.1 of Zookeeper.
Update the previous version bundle name in the supportedBundles present in the kyvosmanagerdata/server/repo/metadata.Kyvos/zookeeper.json file by deleting the new zookeeper version bundle name and then redeploy the Zookeeper to restore managed Zookeeper to version 3.6.1.
For example, to switch to Zookeeper version 3.6.1, before uninstalling the Zookeeper, a key having a value like supportedBundles : [zookeeper-3.7.1.tar.gz] must be updated with supportedBundles : [zookeeper-3.6.1.tar.gz]
Switching to the default non-managed version of Zookeeper
To restore the default non-managed version of Zookeeper on the Kyvos Manager node, which was removed during the uninstallation of Managed Zookeeper, you will need to manually install Zookeeper on the Kyvos Manager node.
Upgrade Graviton JRE for AWS cluster
To upgrade the Graviton JRE version, perform the following post-upgrade steps.
...