Versions Compared

Key

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

...

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

Important

  • From Kyvos 2024.11 release onwards, you can configure Application Gateway from different resource group.

  • While decreasing (terminate) nodes from Kyvos Manager node scaling, you must manually delete the associated disk after the node is deleted.

  • To fetch the Application Gateway from different Resource Group, Kyvos Managed Identity has the Microsoft.Network/applicationGateways/read permission on Application gateway

  • To scale BI Server and Web Portal nodes in Azure Marketplace, the network interface attached to the existing BI Server and Web Portal nodes must be in the same resource group as the BI Server, Web Portal and other resources. If the network interface attached to the BI Server and Web Portal machines exist in a resource group other than the BI Server and Web Portal machine's resource group, assign the Microsoft.Network/virtualNetworks/subnets/join/action permission to MI (Managed Identity) over VN (Virtual Network) by creating a custom role.

  • For Azure Enterprise, create a custom role with the required permissions. While creating a custom role, add the Resource IDs for the following services in the assignable scope:

    • Application Gateway

    • Virtual Network

    • Network Security Group

    • To configure Application Gateway post deployment, create a separate backend pools for Kyvos Manager and Kyvos.

    Once the custom role is created, it must be assigned to each of the above listed services.

Users can scale nodes such as the BI Server, Query Engine, and Web Portal, even if the corresponding nodes are not running on AWS or GCP. However, at least one node must be operational on Azure. For instance, if you scale the Query Engine node, at least one instance of the Query Engine must be active and running.

Increasing Nodes
Anchor
increase
increase

...