We've discussed, and are going to take actions long-term to consolidate into `gitlab-org/cloud-native` for all Cloud Native GitLab work (containers, Helm, Operator, components). This epic encapsulates these actions. After discussion in https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/819#note_591289944, we came to this non-exhaustive outline for organizing projects in the new `cloud-native` group. * gitlab-org * cloud-native * charts * gitlab * gitlab-runner * others, TBD * images (previously CNG) * gitlab-operator * gitlab-runner-operator * gitlab-logger * mirror (for external items/dependencies we mirror into GitLab.com) * images * charts (?) --- Benefits of this structure: * Moves gitlab-operator project out of openshift-specific group * Consolidates all cloud-native items under a single group * Facilitates cross-project epic planning * Improves discoverability * Clarifies broader scope of the projects that comprise cloud-native Drawbacks: * None obvious. Challenges: * Relocation/redirect/mirror of container registry for moved projects * Requires realignment of pipelines, mirrors, source fetching * Documentation will need to be updated that links to source * Various dashboards (issue, epics, SiSense) will need to be updated to point to new project locations