Currently, the calculation doesn't include CUD prices. However, the CAST AI autoscaler can be configured to first pick reserved families to utilize CUDs.
The primary role of the read-only script is to estimate the potential savings realized with CAST AI. This script is open-source, and you can find it here. GitHub - castai/k8s-agent ).
The read-only script won't make any changes to your cluster configuration without explicit permission. It allows us to read basic K8s primitives to give you an estimation of how much savings is possible in a specific cluster. You can read more about it here.
Yes, Reserved Instances are supported for autoscaling.
Zone fields are optional since reservations can be zone-based or region-based. However, note that other providers may include different formats and fields that could be cloud-specific.
Yes, you can get region-based reserved capacity.
Only currently active reservations are taken into account by the CAST AI autoscaler.
Using instances that aren't part of the reservation inventory might happen if:
- reservations are fully utilized,
- the cluster region/zone is not the same,
- the workload requires spot instances,
- the workload requires some special features that aren't available in reserved instances: storage-optimized, compute-optimized, GPU, etc.
The price column displays the initial purchase price for a particular family of reserved instances. Since Reserved Instances (RIs) are prepaid and their cost remains constant, whether you use the virtual machines (VMs) or not, their price is effectively 0 in this instance of time.
As a result, Autoscaler doesn't consider its price when making decisions. Instead, it prioritizes RIs based on other criteria, with the price you input being treated as text without influencing its behavior.
Yes, CAST AI takes into account all instances from clusters onboarded to CAST AI (readonly and no-readonly mode). It doesn't matter if its CAST AI-managed or not.
Updated 14 days ago