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
Castai agent was installed and it is not detecting a spot node, but as on-demand on EKS cluster. do we know how to make castai agent identify it as spot?
The text was updated successfully, but these errors were encountered:
Hi @sumeet-zuora
castai-agent has functionality to collect details about cluster nodes from a cloud provider and identify whether a node is Spot or On-demand. However when it is not able to access cloud API due to missing permissions then there is no way for system to identify nodes' type and as a consequence you see nodes reported as On-demand.
This problem is relevant only for Read-only clusters (Phase 1). Once cluster is fully on-boarded with Cast.AI then we are able to identify nodes' types from the central system and Cast.AI Console present correct status.
To confirm that you are facing this scenario, please check castai-agent logs, there should be an entry like that: failed to determine node lifecycle, some functionality might be limited. If you find this entry then this guide provides requires instructions how to fix it for Read-only clusters.
Please let me know if you have further questions.
Castai agent was installed and it is not detecting a spot node, but as on-demand on EKS cluster. do we know how to make castai agent identify it as spot?
The text was updated successfully, but these errors were encountered: