Versions Compared

Old Version 1

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version 2

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Applies to: (error) Kyvos Enterprise  (error) Kyvos Cloud (SaaS on AWS) (tick) Kyvos AWS Marketplace

(tick) Kyvos Azure Marketplace   (tick) Kyvos GCP Marketplace (tick) Kyvos Single Node Installation (Kyvos SNI)

...

Azure Marketplace Deployments

This section provides information on how to upgrade Kyvos and Kyvos Manager and roll back patches for Azure marketplace deployments.

Anchor
Upgrading
Upgrading

Upgrading Kyvos and Kyvos Manager

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.

To upgrade Kyvos and Kyvos Manager, perform the following steps. 

  1. On the navigation bar, click Application Update > Upgrade. 

  2. The Upgrade page is displayed with the current version details of Kyvos and Kyvos Manager. 

  3. Select the required  Version  from the Upgrade To list to which you want to upgrade.  
    NOTE: In the Upgrade To list, all future versions available for upgrading will be displayed.

  4. To view upgrade options, click the  Show Upgrade Options  link, and configure the following options as needed.

...

  1. To see upgrade history, click the Actions menu (...) and select the View History option.

Anchor
Rollback
Rollback

Rollback 

You can easily roll back both Kyvos and Kyvos Manager applications by simply selecting the required version from the Kyvos Manager portal.

...

  1. Create a manual backup of your existing cluster using the steps explained in the  Upgrading Kyvos Manager and Kyvos  section.

  2. On the navigation pane, click Application Update > Rollback.
    The Rollback page is displayed. 

  3. Click the Select rollback state link. From the displayed dialog box, choose the state to which you want to roll back. You can use the search box to Search for a specific version. The rollback state is selected. You can also change the rollback state using the Change rollback state link. 

  4. Select the required rollback version. 

  5. The Backup Path path shows the path used for creating/restoring a backup of Kyvos states in case of Deploy Upgrade and Deploy Patch/Rollback operations. The backup path should be consistent across all the available systems. You can edit this path using the Modify Backup Path option from the three-dots menu. A ny backup created prior to changing the path remains unaffected and will continue to be available at the same location.

  6. Click the Rollback Now button from the top-right of the page.

  7. On the displayed confirmation message box, select the Start Kyvos Service checkbox to start the service automatically after rollback.

  8. Enter your Kyvos Manager Password to confirm the rollback. Kyvos takes you to the   Operations page   followed by the   Rollback Logs   details page.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

If the Kyvos Manager rollback operation fails, followed by Kyvos rollback, you can resume it by clicking the  Click to resume  option. The Kyvos Manager rollback operation will resume from the point where it last failed. Additionally, you can view the details of the failed operation by clicking the  Click to view details  option.

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFEBE6

Warning

If you are using an external repository for Kyvos, then after the Kyvos version rollback - you need to change to the previous version of the repository using the Switch repository feature.

Anchor
Deployapatch
Deployapatch

Deploy a Patch 

To deploy a patch on an existing Kyvos version, perform the following steps.

...

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

  • You need to manually restore the files uploaded from the Configuration Files page (if any), after upgrading Kyvos.

  • Before applying the Kyvos patch ensure that the Managed Identity attached to the Kyvos Manager node has permission required for updating Functions.

  • You must create a folder structure for patch deployment. Create a folder named "patches" in the current release. Then, create a folder within the "patches" directory with the same name as the patch.
    For example, if the patch name is 'Kyvos2023.2_Patch_134.039.tar.gz', then the folder name should be '2023.2_Patch_134.039'.

Anchor
deleting
deleting

Deleting Kyvos upgrade and patch bundles 

From Kyvos 2023.3 onwards, during Kyvos upgrade and patch processes, the oldest backup bundle will be deleted automatically to retain the newest bundles within the specified limit. Suppose you choose to preserve 6 bundles out of 10 available. In this case, only the 6 most recent bundles will be saved, and the remaining 4 bundles will be deleted. The oldest of these 4 bundles, based on the date they were created, will be deleted first.

To delete a previous state of rollback, use the Manage Backup Bundles option from the three-dots menu.

...

In the Preserve Backup Bundles list, set the count to retain the bundles. 

Points to know

  • If the number of bundles present exceeds the preserved count, the remaining bundle will be automatically selected, indicating that it will be deleted.

  • If the number of bundles equals the retention count, no bundles will be deleted.

  • Bundles can only be deleted by changing the preserve count. Selecting them for deletion is disabled and unsupported. 

  • If the latest backup bundle is a Patch, then the most recent Kyvos bundle will also be preserved.

  • The backup bundles which are created for failed Kyvos upgrade or failed Patch operations will also be there in the list to delete.