chore: clarify cluster_token expiration in gitops examples

Author: Furkhat Kasymov Genii Uulu

examples/aks/aks_cluster_gitops/README.md

@@ -48,7 +48,7 @@ After successful apply, CAST Console UI will be in `Connecting` state.
 terraform output cluster_id  
 terraform output cluster_token
 
-Obtained values are needed for next step
+Obtained values are needed for next step. Note that cluster_token must be used within few hours after creation or it gets expired. It is recommended to install at least castai-agent to keep cluster_token active.
 
 ### Step 4: Deploy Helm chart of CAST Components
 Coponents: `castai-cluster-controller`,`castai-evictor`, `castai-spot-handler`, `castai-kvisor`, `castai-workload-autoscaler`, `castai-pod-pinner` \
@@ -116,4 +116,4 @@ helm upgrade -i castai-kvisor castai-helm/castai-kvisor -n castai-agent \
 
 This example can also be used to import AKS cluster to Terraform which is already onboarded to CAST AI console through [script](https://docs.cast.ai/docs/cluster-onboarding#how-it-works).   
 For importing existing cluster follow steps 1-3 above and change `castai_node_configuration.default` Node Configuration name.
-This would allow to manage already onboarded clusters' CAST AI Node Configurations and Node Templates through IaC.
+This would allow to manage already onboarded clusters' CAST AI Node Configurations and Node Templates through IaC.

examples/eks/eks_cluster_gitops/README.md

@@ -104,7 +104,7 @@ Note generated 'CASTAI_CLUSTER_ID' from outputs
 terraform output cluster_id  
 terraform output cluster_token
 
-Obtained values are needed for next step
+Obtained values are needed for next step. Note that cluster_token must be used within few hours after creation or it gets expired. It is recommended to install at least castai-agent to keep cluster_token active.
 
 ### Step 6: Deploy Helm chart of CAST Components
 Coponents: `castai-cluster-controller`,`castai-evictor`, `castai-spot-handler`, `castai-kvisor`, `castai-workload-autoscaler`, `castai-pod-pinner` \
@@ -172,4 +172,4 @@ helm upgrade -i castai-kvisor castai-helm/castai-kvisor -n castai-agent \
 
 This example can also be used to import EKS cluster to Terraform which is already onboarded to CAST AI console through [script](https://docs.cast.ai/docs/cluster-onboarding#how-it-works).   
 For importing existing cluster follow steps 1-3 above and change `castai_node_configuration.default` Node Configuration name.
-This would allow to manage already onboarded clusters' CAST AI Node Configurations and Node Templates through IaC.
+This would allow to manage already onboarded clusters' CAST AI Node Configurations and Node Templates through IaC.

examples/gke/gke_cluster_gitops/README.md

@@ -48,7 +48,7 @@ Note generated 'CASTAI_CLUSTER_ID' from outputs
 terraform output cluster_id  
 terraform output cluster_token
 
-Obtained values are needed for next step
+Obtained values are needed for next step. Note that cluster_token must be used within few hours after creation or it gets expired. It is recommended to install at least castai-agent to keep cluster_token active.
 
 ### Step 4: Deploy Helm chart of CAST Components
 Coponents: `castai-cluster-controller`,`castai-evictor`, `castai-spot-handler`, `castai-kvisor`, `castai-workload-autoscaler`, `castai-pod-pinner` \
@@ -115,4 +115,4 @@ helm upgrade -i castai-kvisor castai-helm/castai-kvisor -n castai-agent \
 
 This example can also be used to import GKE cluster to Terraform which is already onboarded to CAST AI console through [script](https://docs.cast.ai/docs/cluster-onboarding#how-it-works).   
 For importing existing cluster follow steps 1-3 above and change `castai_node_configuration.default` Node Configuration name.
-This would allow to manage already onboarded clusters' CAST AI Node Configurations and Node Templates through IaC.
+This would allow to manage already onboarded clusters' CAST AI Node Configurations and Node Templates through IaC.