Feature #17249

Updated by Ward Vandewege over 1 year ago

When preemptible instances are used, the CR includes these values:

"scheduling_parameters": {
"preemptible": true

At minimum, costanalyzer should include a 'preemptible' column in the CSV export.

The numbers it reports will be wrong when preemptible instances are used, because the cost data reported is the static unit cost for preemptable instances defined in the config file.

Perhaps it should even just refuse to report amounts for all preemptable instances?