Cluster - Core-hour

The subscription cost that applies to the entire cluster based on total CPU core hours

Formula: Amount of CPU cores * hours * cost model rate

Example: 16 * 24 * 2 = $768

Node - Core-hour

The hourly subscription models that apply to the node based on the total CPU core hours

This metric can also be used with tag-based rates to differentiate Infra and Worker node costs.

Example one calculation: 4 * 24 * 2 = $192

Example two calculations:

- Node 1: 4 * 24 * 2 = $192

- Node 2: 4 * 24 * 4 = $384

Node - Core-month

The monthly subscription models that apply to the node based on the total CPU core hours

This metric can also be used with tag-based rates to differentiate Infra and Worker node costs.

This metric has a daily amortization schedule based on the number of days in a month.

Formula: Amount of CPU cores * cost model rate

Monthly example: 2 * 100 = $200

Daily amortized example for March (31 days): 200/31 = $6.45 per day

Cluster - hour

The subscription cost that applies to a cluster based on running hours. It is not dependent on CPU cores.

A cluster has been running for one full day and has a user-defined rate of $10 per hour.

Formula: Cluster hours * cost model rate

Example: 24 * 10 = $240

VM - Core

To get more precise control over your billing, you can now bill Virtual Machines (VMs) based on the number of physical VM cores that are utilized. This new VM core metric enables you to bill either hourly or monthly. Your system must be running on Operator Release 4.0.0 or later.

Monthly, where the rate is spread out evenly across all days in the month: physical vm cores * (rate / days in month)

Hourly: physical vm cores * rate * number of whole hours reported for vm