Versions Compared

Version Old Version 7 New Version 8
Changes made by

Sarabjeet Kaur

Sarabjeet Kaur

Saved on

Key

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

...

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

Important

  • 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

    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

  • 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 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
panelIconIdatlassian-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 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
configure
configure

...

  • For Azure this functionality is available even when your cluster is shared, and user node pool is dedicated.

  • The option to delete the older node pool is available only for dedicated (non-shared) K8s clusters. 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.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

For Azure, it is available only when the cluster is the shared and user node pool is dedicated

  • 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.

  • 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"

...