Versions Compared

Key

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

...

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

Important

  • From Kyvos 2025.2 onwards, on Azure, you can process data on a dedicated compute cluster if you do not want to use Kubernetes and cannot share the querying engines.

  • Post-deployment, to switch from Kubernetes or Shared Query Engine, ensure the following:

    • You can switch from Kubernetes or a shared query engine to a dedicated compute cluster from Kyvos Manager.

    • You must create a Virtual Machines Scale Set (VMSS) using the Dedicated Compute VMSS template provided by Kyvos.

    • Switching from a dedicated compute cluster to Kubernetes or a

    shared query engine
    • Shared Query Engine is not supported.

  • If using a shared Kubernetes cluster with a dedicated user node pool, ensure that the user node pool has dedicated taints. refer to the Adding Taints and Configure Tolerations in Kyvos worker pods section.

  • In Kyvos 2024.10, for shared K8s cluster, provide the compute namespace that has already been created.

  • You can optionally use the K8s cluster on a shared basis (AWS, Azure, and GCP).

  • If you select Kyvos compute type as Shared Query Engine, then K8s cluster-related information is not applicable.

  • From Kyvos 2024.9 onwards, you can now increase or decrease the Kubernetes node pool Maximum Compute Server Count. This applies only to a dedicated node pool.

  • If you have deployed Kyvos with the Kyvos Native compute cluster, you cannot switch to the External Compute cluster to process semantic models.

...

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

Area

Parameter

Description

Kyvos Native Compute Cluster Configuration

Kyvos Compute Sub-Type

Select one of the following options to select a compute cluster to process the semantic model:

  • Containerized Kubernetes

  • Shared Query Engines

Cluster Details

Cluster Name

Enter the unique Kubernetes cluster name provided while creating it.
Click Fetch Details to get the details of the Kubernetes cluster.

Shared Resources With Multiple Applications

Is Shared Node Pool

  • Select this checkbox to use Kubernetes or User node pool as shared. If this checkbox is selected, the Maximum Compute Server Count field will be disabled.

Node Pool Details

Node Pool Name

Select the node pool name from the list.

Identified Instance Types

The identified instance types are displayed by default. You can also change the default instance type.

Change Node Pool Instance Type

Clicking this link will open the Change Node Pool Instance Type dialog is displayed.

Select the Instance Type from the list and enter Kyvos Manager password to change the node pool instance type.

NOTE: This functionality is available only for dedicated Kubernetes cluster.

K8S Addon Auth Role Name

Enter K8S Addon Auth Role name.

Scaling

Enable Compute Server Scaling

Select this checkbox to enable maximum or minimum compute server for scaling. When you select this checkbox, the following options will be displayed.

  • Minimum Compute Server Count: Select the minimum number of compute Server that will be started initially.

  • Maximum Compute Server Count: Select the maximum number of compute servers to which you want to scale.

NOTE: The Compute Server Count field is displayed if you do not select the Enable Compute Server Scaling checkbox. The scaling will be disabled. You need to enter the compute server count.

Dedicated Namespaces for Kyvos

Compute Namespace

Enter dedicated namespace for Kyvos.

image-20241218-121528.png
Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

Area

Parameter

Description

Kyvos Native Compute Cluster Configuration

Kyvos Compute Sub-Type

Select one of the following options to select a compute cluster to process the semantic model:

  • Containerized Kubernetes

  • Shared Query Engines

  • Dedicated Compute Cluster:

    • Select the required Scale Set from the list that you want to configure.

    • Enter maximum instances count that will run on the selected scale set.

NOTE:

To create a dedicated compute cluster, see the steps mentioned below in this section.

Cluster Details

Cluster Name

Enter the unique Kubernetes cluster name provided while creating it.
Click Fetch Details to get the details of the Kubernetes cluster.

Fetch Clusters by Resource Group

To configure the K8s cluster that is in different Resource Group another than Kyvos.

Clicking the link will open the Fetch Clusters by Resource Group dialog box. Enter Resource Group and click Fetch.

Share Resources With Multiple Applications

Is Shared Cluster

Select this checkbox to use the Shared K8s cluster.
NOTE: If you select this checkbox,

  • The Change Node Pool Instance Type link is not available for changing the node pool instance type.

  • The Maximum Compute Server Count field will be disabled.

Is Shared User Node Pool

Select this checkbox to use the Kubernetes or User node pool as shared.

Node Pool Details

User Node Pool Name

Select the user node pool name from the list.

Identified Instance Types

The identified instance types are displayed by default.

Managed Identity Client ID

Enter the managed identity client ID that is attached to the K8s cluster.

Change Node Pool Instance Type

Clicking this link will open the Change Node Pool Instance Type dialog is displayed. Select the Instance Type from the list and enter Kyvos Manager password to change the node pool instance type.
NOTE: This functionality is available only for dedicated Kubernetes cluster.

Scaling

Enable Compute Server Scaling

Select this checkbox to enable maximum or minimum compute server for scaling. When you select this checkbox, the following options will be displayed.

  • Minimum Compute Server Count: Select the minimum number of compute Server that will be started initially.

  • Maximum Compute Server Count: Select the maximum number of compute servers to which you want to scale.

NOTE: The Compute Server Count field is displayed if you do not select the Enable Compute Server Scaling checkbox. The scaling will be disabled. You need to enter the compute server count.

Dedicated Namespaces for Kyvos

Monitor Namespace

Enter the name of monitoring namespace of your K8s cluster that will be used for Kyvos monitoring.
NOTE: The namespace must be dedicatedly used only for Kyvos.

Compute Namespace

Enter the name of compute namespace of your K8s cluster that will be used for Kyvos computing.

NOTE: The namespace must be dedicatedly used only for Kyvos.

image-20250225-063830.png
Aura tab
summaryGCP
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

Area

Parameter

Description

Kyvos Native Compute Cluster Configuration

Kyvos Compute Sub Type

Select one of the following options to select a compute cluster to process the semantic model:

  • Containerized Kubernetes: If you select this option, you will see the Kubernetes cluster-related details you need to specify.

  • Shared Query Engines: If you select this option, you will see the following options:

    1. Enable External Metastore: This checkbox enables external metastore in the Kyvos cluster.

    2. Thrift URL: After enabling external metastore you need to specify the Thrift URL.

Cluster Details

Kubernetes Cluster Name

Enter the unique Kubernetes cluster name provided while creating it.
Click Fetch Details to get the details of the Kubernetes cluster.

Shared Resources With Multiple Applications

Is Shared Node Pool

  • Select this checkbox to use Kubernetes or User node pool as shared. If this checkbox is selected, the Maximum Compute Server Count field will be disabled.

Node Pool Details

Node Pool Name

Select the node pool name from the list.

Identified Instance Types

The identified instance types are displayed by default. You can also change the default instance type.

Change Node Pool Instance Type

Clicking this link will open the Change Node Pool Instance Type dialog is displayed.

Select the Instance Type from the list and enter Kyvos Manager password to change the node pool instance type.

NOTE:

  • This functionality is available only for dedicated Kubernetes cluster.

  • To change Kubernetes node pool instance type, the compute.machineTypes.list permission is required.

Scaling

Enable Compute Server Scaling

Select this checkbox to enable maximum or minimum compute server for scaling. When you select this checkbox, the following options will be displayed.

  • Minimum Compute Server Count: Select the minimum number of compute Server that will be started initially.

  • Maximum Compute Server Count: Select the maximum number of compute servers to which you want to scale.

NOTE: The Compute Server Count field is displayed if you do not select the Enable Compute Server Scaling checkbox. The scaling will be disabled. You need to enter the compute server count.

Dedicated Namespaces for Kyvos

Compute Namespace

Enter the name of compute namespace of your K8s cluster that will be used for Kyvos computing.

NOTE: The namespace must be dedicatedly used only for Kyvos.

image-20241219-084001.png

Aura tab
summaryOn-Premises
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJPbi1QcmVtaXNlcyUyMiU3RA==

For Kyvos Compute Sub Type, the Shared Query Engines sub type is displayed in read-only mode.

image-20241127-084025.png

...

  1. Click the cluster name > Kyvos and Ecosystem > Compute Cluster on the navigation pane to view this information.

  2. On the Compute Cluster page, click the Click to change link on the right of the page. The following dialog box is displayed.

    image-20241127-073612.png
  3. Select the required Default Compute Type from the list.

  4. Enter your Kyvos Manager password.

  5. Click Save. The default compute cluster is configured.

Creating a dedicated compute cluster
Anchor
creating
creating

  1. For creating a dedicated compute cluster, download the JSON file, which is available in the Azure Installation Files folder.

  2. Go to Azure portal.

  3. Search for ‘Deploy a custom template’ in the search bar.

  4. Upload the downloaded JSON file.

  5. Provide the same parameter that you mentioned while creating Kyvos cluster.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

The resource group of the dedicated compute cluster must be the same as the Kyvos cluster deployment resource group.