We currently normalize OpenShift data to UTC.

Cloud data comes in whatever timezone the cloud region where the account was created is.

There's a number of features that may suffer the impact of wrong or unaligned timezones: constant currency (COST-3358), lifecycle of price lists (COST-575), budgets (COST-219), etc

This feature is about researching, proposing and implementing any required changes to make sure we always apply exactly the right price to the right resource at the right moment in time, whatever the timezone where the data was acquired, whatever the timezone where the resource was billed and whatever the timezone where everything was ingested and processed.