Using Existing Kubernetes Cluster (No-Spark)

Using existing Kubernetes cluster

Points to know before using an existing Kubernetes (K8s) cluster

1. Shared cluster is not supported on AWS and GCP.

2. Namespaces must be fixed for the existing K8s cluster as kyvos-compute and kyvos-monitoring on AWS and GCP

3. Node pool of Kubernetes cluster must be for dedicated Kyvos use.

4. Even if a dedicated node pool is needed for Kyvos, currently, a single Kubernetes cluster can be used with any single Kyvos cluster. This means that one dedicated node pool of a K8s cluster cannot be used with one Kyvos cluster, and another dedicated node pool of the same K8s cluster cannot be used with another Kyvos cluster.

5. Node pool used for Kyvos must have single instance type used for pool.

6. Node pool with multiple instance type is not supported.

7. Currently, Azure is not supported for existing Kubernetes cluster in any of the following cases:

   1. Fresh automated deployment

   2. Fresh wizard- based deployment

8. Instance type of Node pool must be of 4 minimum cores & 16 GB memory requirement.

9. There must be required permissions to list Kubernetes clusters and their node pools; without these permissions, the input will be converted to a text input rather than a dropdown.

10. Node pool for GCP Kubernetes cluster must be of single zone. Multi-zone node pool is not supported.

Support for using existing Kubernetes cluster with Kyvos

1. The name of a Kubernetes cluster provided by the user can be arbitrary and is not required to be a fixed name.

2. The name of (user) node pool can be arbitrary and is not required to be a fixed name. Thus, user provided pool can be used with Kyvos.

3. Regardless of the method used to create a pre-existing Kubernetes cluster (UI, Terraform, ARM/CFT), it can be used with Kyvos.

4. The role or identity used for creating a Kubernetes cluster may be identical to or different from the one used for creating Kyvos resources. However, the Kyvos role possesses the required permissions to access the Kubernetes cluster, it will function properly.

5. If user’s Kubernetes cluster in different VPC then peering must be required.

6. The security group and subnet of a Kubernetes cluster must be the same. However, if the security group or subnet of the provided Kubernetes cluster differs, it can still be used after permissions to access that subnet and the required ports are added to the security group used in the Kyvos cluster.