Kubeslice Controller
Note that the information provided on this page represents the minimum requirements for installing the product. It is essential to understand that these requirements may vary depending on the specific workload of each customer. However, following these minimum requirements will ensure a successful installation of the product.
| Cluster Requirements | 1 Kubernetes Cluster |
| Node Requirements | KubeSlice needs at least one node with a minimum of 2 vCPUs and 1.25 Gi of RAM available. We highly recommend creating a separate NodePool for KubeSlice components to improve performance and simplify management. |
| Supported Kubernetes Versions | 1.26, 1.27, and 1.28 |
| Supported Kubernetes Services | Azure Kubernetes Service (AKS), AWS Elastic Kubernetes Service (EKS), Google Kubernetes Engine (GKE), and Rancher Kubernetes Engine (RKE) |
| Required Helm Version | 3.7.0 |
KubeSlice has been tested on AKS, GKE, and EKS, but it should run in any Kubernetes environment with the supported Kubernetes versions.
In an intra-slice scenario, a single cluster can serve as both a controller cluster and a worker cluster. This allows KubeSlice to segment the cluster into application slices. This enables you to better manage and isolate your applications, improving the overall efficiency and performance of your cluster.