Corrective action: Enforce required labels on hosts
Summary
We have apparently multiple different teams using the service label for important things (including delivery) and nothing in code that confirms that people aren't changing it.
In addition to the other issue to standardize and document the label usage, we should enforce any required labels using conftest as part of the CI pipelines.
Related Incident(s)
Originating issue(s): gitlab-com/gl-infra/production#ISSUE_ID
Desired Outcome/Acceptance Criteria
Associated Services
Corrective Action Issue Checklist
-
Link the incident(s) this corrective action arose from -
Give context for what problem this corrective action is trying to prevent re-occurring -
Assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4') -
Assign a priority (this will default to 'Reliability::P4' but should match the severity of the related incident) -
Assign a service label