Let's consider moving the GitLab Operator project out of the `gl-opensfhift` group into a non-OpenShift-specific group. For example: `gitlab-org/gitlab-operator` While we're on the topic, this reminds me of a discussion that @WarheadsSE mentioned regarding a group named something similar to `cloud-native`, which could house the Operator as well as CNG, Charts, etc. ### TL;DR 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 issue will close* when we move `gitlab-org/gl-openshift/gitlab-operator` to `gitlab-org/cloud-native/gitlab-operator`. ### Action items - [x] Epic to track [larger work of consolidation](https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/819#note_591285824) - [x] Creation of `gitlab-org/cloud-native` sub-group - [x] Locate process / DRI capable of creating the group. - [x] Group is created - [x] Team granted appropriate accesses - [x] Transfer https://gitlab.com/gitlab-org/gl-openshift/gitlab-operator to https://gitlab.com/gitlab-org/cloud-native/gitlab-operator - [x] sync container registry content to temp - [x] delete container registries from origin - [x] transfer project - [x] ensure permissions of team - [x] sync container registry content to final home (using `registry-migration.gitlab-ci.yml` in https://gitlab.com/gitlab-org/gl-openshift/gitlab-operator/-/merge_requests/165, see details [below](#use-temporary-ci-configuration)) - [x] delete container registries from temp - [x] Replace all ENV / token configuration - [x] Update code references to point to new repository location: https://gitlab.com/gitlab-org/cloud-native/gitlab-operator/-/merge_requests/167 #### Use temporary CI configuration https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path