...
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
Important 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 Azure, you can optionally use the K8s cluster on a shared basis. This functionality is not applicable to AWS and GCP. For shared K8s cluster, provide the compute and monitoring namespace that has already been created. For AWS and GCP, namespace names are fixed; hence, fields are disabled.
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 is applicable only to dedicated K8s cluster. If you have deployed Kyvos with the Kyvos Native compute cluster, you cannot switch to the External Compute cluster to process semantic models.
|
...
The Kubernetes cluster must be in the same region in all cloud environments.
For GCP, the Kubernetes must be in the same project.
For Azure, the Kubernetes cluster is supported even in a different Resource Group.
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
|
Note To fetch the Kubernetes cluster from a different resource group, ensure that Kyvos Managed Identity must have reader on that Kubernetes. |
For shared K8s cluster, provide the compute and monitoring namespace already created. Currently, only in the case of a dedicated (non-shared) K8s cluster will the system attempt to create a compute and monitoring namespace with the provided name on Azure Enterprise. For AWS and GCP, namespaces names are fixed, hence, those are disabled fields.
For AWS and GCP, the K8s cluster must be used in dedicated mode. Hence, the Shared cluster check box is disabled.
...
| Aura tab collection |
|---|
| params | JTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA== |
|---|
|
| Aura tab |
|---|
| summary | AWS |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q= |
|---|
|
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 | 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 | | 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 Removed Image Added| Aura tab |
|---|
| summary | Azure |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA== |
|---|
|
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. | | 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 Select the system node pool name from the list. | Node Pool Details | System Node Pool Name | | | 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. | Kyvos 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 Removed Image Added| Aura tab |
|---|
| summary | GCP |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q= |
|---|
|
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: Enable External Metastore: This checkbox enables external metastore in the Kyvos cluster. 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 | | 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. |
 Image Removed | 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 Added| Aura tab |
|---|
| summary | On-Premises |
|---|
| params | JTdCJTIydGl0bGUlMjIlM0ElMjJPbi1QcmVtaXNlcyUyMiU3RA== |
|---|
|
For Kyvos Compute Sub Type, the Shared Query Engines sub type is displayed in read-only mode.  Image Modified |
External: To know more about the External Compute Cluster, see the Hadoop Ecosystem Configuration section.
...
You can Change the Node Pool Instance Type for Kyvos Enterprise (AWS, Azure, and GCP). From Kyvos 2024.11 onwards, you can change default compute cluster sub type as Shared Query Engine.
This functionality is only available only for dedicated (non-shared) K8s clustersuser node pool.
The option to delete the older node pool is available only for dedicated (non-shared) K8s clustersuser node pool. If node pool deletion permissions are there, after selecting node pool deletion, it will be deleted automatically to avoid manual deletion of node pool from external to system.
If you are not deleting the older node pool, ensure to remove the taints from older node pool. If you want to configure new taints and toleration, then refer the Adding Taints and Configure Tolerations in Kyvos worker pods
The instance type configured for a node pool must be associated with a single instance type, even if multiple instance types are supported for the node pool in any cloud environment.
Changing the instance type for a Kubernetes (K8s) cluster node pool should only be supported for the node pool where Kyvos jobs will execute. Therefore, there will be no support for changing the instance type of any other node pool not configured in Kyvos. For Azure, only the user node pool will support instance type changes, while the system node pool will not support such changes.
For GCP, the compute.machineTypes.list permission is required to change the Kubernetes node pool instance type.
For Azure, following permissions are required to change node pool instance type.
"Microsoft.ContainerService/managedClusters/agentPools/write",
"Microsoft.ContainerService/managedClusters/agentPools/read",
"Microsoft.ContainerService/managedClusters/agentPools/delete"
To support K8s cluster node pool instance type, change, add below required permissions to AWS Automated and Wizard based deployment IAM role.
...
Click the cluster name > Kyvos and Ecosystem > Compute Cluster on the navigation pane to view this information.
On the Compute Cluster page, click the Click to change link on the right of the page. The following dialog box is displayed.
Select the required Default Compute Type from the list.
Enter your Kyvos Manager password.
Click Save. The default compute cluster is configured.
...
