Add gl_cost_owner label to labeling strategy

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

Summary

• Adds the gl_cost_owner label to the Cloud Cost Utilization labeling strategy
• This label identifies a VP-level owner for cloud resources across both GCP and AWS
• Updates the page scope to reflect coverage of both GCP and AWS

What is gl_cost_owner?

The gl_cost_owner label provides executive accountability by associating cloud costs with a VP-level owner. Unlike gl_service which is scoped to GCP, gl_cost_owner applies to both GCP and AWS, giving consistent cross-cloud ownership visibility.

Changes

• Updated page description and scope warning to reflect both GCP and AWS
• Added new "VP-level ownership allocation" section documenting the label's purpose, format, and usage

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Add gl_cost_owner label to labeling strategy

Introduce the gl_cost_owner label for VP-level ownership of cloud resources across both GCP and AWS.

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

---