The new feature (https://help.apptio.com/en-us/cloudability/whats-new.htm - May 19th) is promising but missed to cover all aspects  for proper chargeback.

The costs associated with the container specific EBS volumes aren't getting distributed via the new metrices. These costs are being distributed from the Insights -> Containers cost allocation. 

Does Apptio plan to fix this ?

This is frustrating, we have the same issue too. We're experimenting with a methodology that takes EBS cost and management services like istio and adding them into an unallocated pool per cluster.  We then charge each namespace a proportional 'tax' for these resources. This is an external process, and is a fixed tax as opposed to a 'fairshare'.  It would be nice if Cloudability could offer some capability like that.  I'm sure it has to do with the different  way the k8 agent obtains data vs. the rest of the tool- and how to combine them.  

However for EBS, the documentation explains "Not all cluster costs are attributed to a specific namespace within a cost report. For example, in AWS deployments, EBS costs of attached volumes are instead considered a cluster cost and therefore shown with a (not set) value for Namespace. The same is true for Storage resources in Azure. ".   https://help.apptio.com/en-us/cloudability/product/k8s-cost-allocation.htm

I'm wondering if  the EBS volumes could be labeled within the k8 cluster and the agent could read that ??