Production Engineering sub-group re-organization

Overview

This issue was split out of https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues/26100. See that issue for some early discussion.

Problem

With the recent re-org in Infrastructure Platforms, the Production Engineering group has taken a new shape.

The new Production Engineering group consists of:

• Cloud Connector
• Foundations
• Observability
• Ops
• Runway

Previously, we have used a set of sub-groups in gitlab-org for organizing and pinging team members:

• https://gitlab.com/gitlab-org/production-engineering
• https://gitlab.com/gitlab-org/scalability
• https://gitlab.com/gitlab-org/cloud-connector-team

Proposal

We should combine sub-groups to reflect the current group structure with the following subgroups:

gitlab-org/production-engineering/foundations
gitlab-org/production-engineering/ops
gitlab-org/production-engineering/runway
gitlab-org/production-engineering/cloud-connector
gitlab-org/production-engineering/observability
gitlab-org/production-engineering/managers
gitlab-org/production-engineering/leads

Some of these groups are managed in https://gitlab.com/gitlab-com/gl-infra/infra-mgmt, for example scalability.yaml and production-engineering.yaml. infra-mgmt then provides these groups specific role access to their underlying projects.

Implementation plan

• Add Runway, Observability, and Cloud Connector to production-engineering.yaml in order to achieve most of (1.) from above. https://gitlab.com/gitlab-com/gl-infra/infra-mgmt/-/merge_requests/1391
• Set up a way to create the gitlab-org/production-engineering/leads group which will include all Staff+ engineers and managers within the group. https://gitlab.com/gitlab-com/gl-infra/infra-mgmt/-/merge_requests/1393
• Cleanup the older scalability.yaml and adjust all underlying groups and projects that reference it within infra-mgmt appropriately