You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/eks/eks_cluster_live_migration/README.MD
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,15 @@ CAST AI modules are places in one umbrella module that can be reused for differe
9
9
Example configuration should be analysed in the following order:
10
10
1. Create VPC - `vpc.tf`
11
11
2. Create EKS cluster - `eks.tf`
12
-
3. Create IAM and other CAST AI related resources to connect EKS cluster to CAST AI, configure Autoscaler and Node Configurations - `castai.tf`
12
+
3. Create IAM and other CAST AI related resources to connect EKS cluster to CAST AI, configure Autoscaler and Node Configurations - `castai.tf` and `modules/castai`.
13
+
14
+
CLM is enabled by having:
15
+
1.`clm_enabled = true` in `modules/castai/main.tf` in the CAST AI node template.
16
+
2.`container_runtime = "containerd"` and `eks_image_family = "al2023"` in the CAST AI node configuration.
17
+
3.`install_live = true` (`install_live = var.install_helm_live`, default value is `true`) in the CAST AI module configuration (`module "castai-eks-cluster"`).
18
+
All are in the `modules/castai/main.tf` file.
19
+
20
+
All other EKS/CAST AI resources mostly manage the EKS cluster and its connection to CAST AI, not specifically the CLM feature.
0 commit comments