Types of Allocation Rules

Yotascale provides a granular way of creating allocation rules to help with getting full control of the allocation of cost line items based on the types of charges.

There is how the different charges are are allocated:

Cloud Services: these are resource. service, account, region, provider allocations based on usage (on-demand, pay-as-you-go).
Container Services: these are costs classified as container related spending for things like clusters (by name or type), container labels, namespaces
Service Charges: these include a variety of special charges, usually a one-time-charge per month. Most common are: Credits, Refunds, Taxes, One-Time-Charge, Support
Purchages: these are usually a monthly, quarter, year purchases. They include Premium Support, Marketplace purchases (or Fees)
Commitments: these are recurring, or once a period, costs associated with Reservation, Savings Plans, etc.

Any of these costs can be allocated directly to a node, or indirectly, via Shared Cost Allocation.

For Direct, it means 100% allocation of the costs to a node.

For Shared-Cost-Allocation, it can be done vi:

Custom Percentage: to multiple nodes (you should make sure it adds up 100%)
Even Split: each node gets an event split of the cost of the resource/charge. All the children of the node with this rule will have a dynamic costs based on usage
Proportional (to usage): each nodes get a portion of the cost based on the respective nodes. All the children of the node with this rule will have a dynamic costs based on usage

Q&A

How do allocated only the usage based costs?

Include only the “Cloud Service” costs. In this example, we’re allocating only the resources that have the tag 'environment' equal to 'production'

How do I allocated all the costs of an account to a node?

To allocate all costs, including discounts, credits, taxes, commitments, marketplace, etc, you need to include a rule for each category. Here is an example of allocation all the “Production Account” costs

How do I allocated my support costs proportionally to usage?

This is a common use case, to shared the costs of support to all business context, based on their respective usage. Here is an example of apply the shared costs of support from the top “/(root)” down to each node