/
Managing Cluster

Managing Cluster

This section contains details about a cluster created for Kyvos, which is a set of resources created in the Kyvos-managed AWS environment. It includes functionalities related to subscriptions, namely creating, viewing, deleting, starting/stopping, and viewing history for any cluster. The Kyvos SaaS Portal interacts with Kyvos Manager and Kyvos Web Portal to fetch current cluster configurations, cost/usage consumption by the cluster, and the deployment status of the Kyvos cluster.

Viewing cluster details

To view cluster details, perform the following steps.

  1. On the navigation bar, click Clusters. The Clusters page is displayed.

    • Case 1: For the first time login or when no cluster is created, the following page is displayed.

      image-20250508-093820.png

    • Case 2: After creating clusters, a list will display clusters that have been added using the required subscription.

  2. Clicking a cluster will display the following details on the right of the page.

    image-20250508-101836.png

    • Status: Displays a current state of the cluster, such as Offline, Online and Failed.

    • Subscription: Displays a subscription name used to create the cluster. Clicking the subscription name will redirect you to the Subscriptions page and the subscription details will display on the right of the page.

    • Region: Displays the region in which the cluster is deployed.

    • Open Kyvos Manager: Clicking the Open Kyvos Manager link will redirect you to the Kyvos Manager Login page.
      See the Kyvos Manager Management and Monitoring Guide for more details.

    • Open Kyvos Web Portal: Clicking the Open Kyvos Web Portal link will redirect you to the Kyvos Login page.

  3. Additionally, you can also view the Overview, Cost Analysis, Audit Logs, and Deployment Details tabs to view further details of the selected cluster.
    From Kyvos SaaS portal 1.7.0, you can now change the compute type from Kyvos Manager on the Compute Cluster page.

    Note: The compute type displayed in the Deployment Details section will remain unchanged when the compute type is modified from Kyvos Manager. Changes to the compute type will be performed by Kyvos Administrators, Kyvos Support personnel, Kyvos DevOps teams, and users who possess administrative rights in Kyvos Manager.

Deploying a new cluster

You can create and deploy a new cluster. After deploying the cluster, the deployment details are displayed.

From Kyvos SaaS portal 1.7.0, you must maintain a minimum balance relative to the clusters being deployed. The minimum balance is calculated as N × $100, where N is the total number of clusters being deployed or already deployed.

To deploy a cluster, perform the following steps.

  1. On the navigation bar, click Clusters.

  2. Click the New button. The New Cluster dialog is displayed.

  3. Select the required Subscription from the list. The current balance of the selected subscription is displayed.

Note

If the current balance for the selected subscription is low, first you must add funds to that subscription to create a new cluster.

  1. Enter the Cluster Name.

  2. Enter Description of the cluster if required.

  3. Select AWS or Azure from the Cloud Provider list where the cluster needs to be created.

  4. Select the geographic location from the Region list where your clusters will be deployed.

  5. Enter CIDR range.

Note

CIDR range starts from 10.0.0.0/16 to 10.255.255.255/16. You will receive an auto-assigned CIDR based on availability, but it can be modified within the permitted range if needed.

  1. Select the required Kyvos version from the list.

Kyvos does not support Kubernetes (no-Spark) and EMR (Spark-based) deployments.

  1. Select the Dedicated Compute or Shared Query Engine from the Kyvos Version list. This is applicable only when you create a new cluster.

    • If you select cloud provider as AWS, the Kyvos version 25.5 and 25.6 will be displayed.

    • If you select cloud provider as Azure, the Kyvos version 25.4.1 and 25.6 will be displayed.

    • Shared Query Engine mode, when all the data processing will be completed on the QE instance itself. 

    • Dedicated Compute mode, a separate scaling group will be created, and the same will be used for data processing jobs. 

  2. Select the System Availability checkbox.

    1. If this is enabled, two Web Portals, two BI Server nodes, and a minimum of two Query Engines are deployed across multiple availability zones. The Query Engines instances will be auto selected as 2. You can also modify the number of Query Engine instances as needed. The maximum Query Engine can be selected as 5.

    2. If this is disabled, the deployment consists of one Web Portal, one BI Server node, and the specified number of Query Engines—all in a single availability zone to optimize cost. You can specify the number of Query Engines (QEs) between 1 to 5 to be provisioned during deployment based on workload and performance requirements.

Note

With high availability enabled, the system remains operational during availability zone failures.

  1. Select the Disaster Recovery checkbox to enable or disable backup and disaster recovery services for the region. The Disaster Recovery for Azure will be disabled.

  2. In the Login Credentials for Kyvos Manager and Kyvos Web Portal, enter Password.

  3. Retype the password to confirm. Ensure that the user name (Admin) and password will remain the same for the Kyvos Manager and Kyvos Web Portal.

  4. Click Review and Deploy to create and deploy cluster

Note

  • The Backup region must be AWS Region.

  • The password must be:

    • Minimum of 8 characters

    • At least one capital letter

    • At least one special character

    • At least one number

For example, PassW0rd@100

Once the cluster is deployed, the Kyvos SaaS Portal will give you access to Kyvos Manager and Kyvos Web Portal. User must provide the password setup for cluster to log into these portals.

image-20250708-101812.png

Once the cluster is deployed, you can view the deploying details.

Copyright Kyvos, Inc. 2025. All rights reserved.