Versions Compared

Old Version 1

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version Current

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

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

...

  • The cluster deployed with earlier releases, before adding or removing Kyvos Manager Service, ensure that the permissions required for Load Balancer entries manipulation are added to the role.
    See the Permissions for Load Balancer entries manipulation section.

  • Adding Kyvos Manager (KM) instances is supported only on nodes with Kyvos Web Portal as a cost optimization strategy. Thus, Kyvos Manager HA requires Web Portal HA as a precondition.

  • For Kyvos Manager HA, the Zookeeper must be up and running.

  • Each node in a cloud cluster must have the respective CLI command (aws, azcopy, gsutil), while on-premises, it must have the HDFS command and access to HDFS.

  • For cloud environments, a Load balancer must be configured in the cluster. If the Load balancer is not configured, you need to provide its details.

    • For AWS, the Load Balancer needs to be from the same region in which other resources of the Kyvos cluster are deployed.

    • For Azure, the Load Balancer needs to be from the same resource group and region in which other resources of the Kyvos cluster are deployed.

    • For GCP, the Load Balancer needs to be in the same project and region in which other resources of the Kyvos cluster are deployed.

  • Irrespective of the type of repository used for Kyvos Manager, the repository must be accessible from all Kyvos Manager nodes.

  • All newly added instances of Kyvos Manager must have the same permissions (IAM Role, Managed Identity) and network access permissions (Security Group, Local Firewall) as the Kyvos Manager node.

  • To enable the Kyvos Manager High Availability mode, navigate to the Kyvos Manager Settings > Kyvos Manager Properties.On the Kyvos Manager Properties page, search for the ENABLE_KM_HA property, and then set the value of the ENABLE_KM_HA property to ‘yes.’ By default, this property is set to ‘no,’ which means that the Kyvos Manager HA mode is disabled and will not be displayed on the Kyvos Manager Dashboard. Therefore, if you want to make the Kyvos Manager HA available, you need to update the value of this property to ‘yes.’ After enabling the Kyvos Manager High Availability through this property, Kyvos Manager will restart. After restarting Kyvos Manager, the Kyvos Manager Disaster Recovery script must be pushed, as shown below.

    image-20240124-145458.png

...

To learn how to add Kyvos Manager nodes, refer to the https://kyvosdocumentation.atlassian.net/wiki/spaces/KD20242KD20243/pages/69454371171176940/Managing+Services+Mapping+and+Nodes#addingKMservice section.

...