Verified Commit a7b0c6a1 authored by Andreas Brandl's avatar Andreas Brandl
Browse files

Add gl_service label to infrastructure labels and tags 

Add gl_service as an optional label that links resources to entries in
the GitLab service catalog for ownership and operational responsibility.

This label supports cost allocation and incident management by establishing
clear service ownership. The label is optional and should reference valid
service catalog entries.
parent cecc3bd1

content/handbook/company/infrastructure-standards/labels-tags.md

+25 −0
Original line number Diff line number Diff line
@@ -25,6 +25,7 @@ In labels and tags for specific realms should be prefixed with the realm prefix. 
| `gl_dept_group`          | Required                             | GitLab Department Group | [Usage Documentation](#gitlab-department-group-gl_dept_group)                       |

| `gl_product_stage`       | Optional                             | GitLab Product Stage    | [Usage Documentation](#gitlab-product-stage-gl_product_stage)                       |

| `gl_product_category`    | Required                             | GitLab Product Category | [Usage Documentation](#gitlab-product-category-gl_product_category)                       |

| `gl_service`             | Optional                             | GitLab Service          | [Usage Documentation](#service-catalog-reference-gl_service)                            |

| `gl_resource_type`       | Optional                             | Cloud Resource Type     | [Usage Documentation](#resource-type-gl_resource_type)                              |

| `gl_resource_group`      | Optional                             | Cloud Resource Group    | [Usage Documentation](#resource-name-gl_resource_group)                             |

| `gl_resource_name`       | Optional                             | Cloud Resource Name     | [Usage Documentation](#resource-name-gl_resource_name)                              |
@@ -62,6 +63,7 @@ Here is a summary of changes made during the design of these standards based on 
- The `sales-cs` realm was consolidated into the `business-tech` realm since the Demo Systems infrastructure is now managed by Business Technology.

- The `infra-shared-services` realm was added for top-level infrastructure management.

- We now allow short-term and long-term [working groups](/handbook/company/working-groups/) to use the `gl_dept_group` label with the prefix of `wg-` and an easily understood name of their choice (no codenames).

- In 2026, we [added](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/17829) `gl_service` as a reference to the GitLab service catalog.



## Environment Realm (`gl_realm`)
@@ -442,6 +444,29 @@ Product categories should match one of the categories defined in [`categories.ym 


By providing this value, costs can be directly mapped back to a specific set of features, as well as a set of owners within both Product and Engineering.



## Service Catalog Reference (`gl_service`)



{{% alert color="info" %}}

This label/tag is optional.

{{% /alert %}}



```terraform

gl_service: 'ci-runners'

```



This label links resources to entries in the [GitLab service catalog](https://gitlab.com/gitlab-com/runbooks/-/blob/master/services/service-catalog.yml), establishing clear ownership and operational responsibility for cost allocation and incident management.



### Expected Values



Service catalog entries should match entries in the GitLab service catalog. Example values include:



- `ci-runners` - GitLab Runner service

- `ci-jobs-api` - CI Jobs API service

- `frontend` - Frontend application service

- `patroni-ci` - Patroni cluster for CI



> Please consult the service catalog for the complete list of valid service catalog entries. Consider [adding to the catalog](https://gitlab.com/gitlab-com/runbooks/-/blob/master/services/README.md?ref_type=heads) if a service is not represented yet.



## GitLab Department Group (`gl_dept_group`)



{{% alert color="success" %}}