...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
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. |
...
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 | ||||||
|---|---|---|---|---|---|---|
| ||||||
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 comput 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.
Configure Kyvos Native Cluster configurations
| Anchor | ||||
|---|---|---|---|---|
|
...
Click the cluster name > Kyvos and Ecosystem > Compute Cluster on the navigation pane to view this information.
The Compute Cluster page displays the two tabs:
Kyvos Native: To process the semantic model using Kyvos native, click this tab to select the containerized Kubernetes or Shared Query Engines as a compute cluster.
External: Click this tab to view the External compute clusterdetails.
Enter the details as:
...
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 Azure, following permissions are required to change the Kubernetes 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.
Create Node Group
"eks:CreateNodegroup"
"eks:TagResource"
"iam:GetRole"
"ec2:DescribeKeyPairs"Delete Node Group
"eks:DeleteNodegroup"
...