Cost Management supports OpenShift clusters running on-prem and on clouds. 

If Mr User creates Sources for the cloud accounts where the on-cloud clusters are running, we will distribute the relevant cost items from the cloud bill to the cloud objects (node, cluster, project, tag, etc). 

When creating a cost model, you can specify what source (or price list) to attach to that cost model. In the Cost Model page, you can check what sources are associated to a cost model (more than one source may be attached to the same cost model). 

Unfortunately, we do not really have a great way to show the reverse: what cloud account (source) or price list is generating that costs that will be attributed to my cluster/project/node/tag. This recently was the cause of a customer case: Mr Customer has 19 clusters but only 13 of them were getting cloud costs because they had forgot to add the cloud accounts for the remaining 6 clusters, yet there was no indication of this problem. 

We should: 

1. Display where a cluster is running, to the best of our knowledge: AWS, Azure, GCP, OCI or on-prem 
2. Show where the costs for a cluster/node/project/tag are coming from: what cloud account(s) (or price list(s)) and source(s). More than one is possible, since my project might be running on several clusters across several clouds, or (probably exotical) my cluster may have clusters on different clouds/regions/accounts. 
3. When no costs are being distributed to a cluster/node/project/tag, show a warning in the OpenShift page. Same when costs are missing, e. g. when one of the clusters running that project is receiving costs but another cluster running that project is not receiving costs. 
   1. Should we also implement a notification? Not having costs attached to a cluster/node/project/tag is not necessarily a wrong thing: I may be on-prem and be only interested in usage information, hence no price list or cloud account attached.