Ensure environments in `gitlab-com` repository match new naming structure
In #2506 (closed) we determined that the environment naming structure we wish to use is $environment/$cluster/$service
. This issue is to track the work needed to convert the gitlab-com
CI setup so that the GitLab environments used match this format, across both the gitlab.com and ops.gitlab.net instances.
As the gitlab-com
is a monorepo for almost all GitLab.com services at the moment, we will use the name gitlab
. To this end, the final list environments should be
- pre/pre-gitlab-gke/gitlab
- gstg/gstg-gitlab-gke/gitlab
- gstg/gstg-us-east1-b/gitlab
- gstg/gstg-us-east1-c/gitlab
- gstg/gstg-us-east1-d/gitlab
- gstg-cny/gstg-gitlab-gke/gitlab
- gprd/gprd-gitlab-gke/gitlab
- gprd/gprd-us-east1-b/gitlab
- gprd/gprd-us-east1-c/gitlab
- gprd/gprd-us-east1-d/gitlab
- gprd-cny/gprd-gitlab-gke/gitlab
TODO
-
Update gitlab-com
.gitlab-ci.yml
to make sure the environments referenced by the deploy jobs are matching the standard -
Modify the diff/dry-run jobs to use the action: access
setting on the environment stanza to avoid those jobs creating a deployment object https://docs.gitlab.com/ee/ci/environments/index.html#access-an-environment-for-preparation-or-verification-purposes -
Remove the old and now unneeded environments from the GitLab UI at https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/environments and https://ops.gitlab.net/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/environments -
Remove the legacy Kubernetes integration pieces at https://ops.gitlab.net/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/clusters?tab=certificate_based (to minimise confusion) -
Confirm that auto deploys and regular deploys still continue to function
Edited by Graeme Gillies