Shared runner cost allocation

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Enterprises that provide shared runners need to be able to determine which projects/teams/departments are consuming these resources, and chargeback the expense.

Target audience

• Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney

• Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha

• Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon

• Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney

• Department manager

• Accounting

Further details

From &503 (comment 117642089):

I've head at one of our top 5 customers they need cost allocation for shared autoscaling CI runners. I don't think they use Kubernetes.

This is related to cluster cost optimization, but seems tangential and distinct, especially since many shared runners aren't in clusters and this isn't strictly about optimizing spend, but allocating spend.

Proposal

What does success look like, and how can we measure that?

What is the type of buyer?

(Which leads to: in which enterprise tier should this feature go see https://about.gitlab.com/handbook/product/pricing/#four-tiers )

Links / references