Create new GCS bucket for the container registry in pre-prod
Related to gitlab-org&5392 (closed).
As we approach the deployment of the new registry with a metadata database and online garbage collection to pre-production, we'll need a new GCS bucket for the registry.
The idea is to make the new version of the registry use this (clean) bucket and then import the non-dangling data from the old one. Keeping the old bucket around and intact guarantees that we can rollback to it or simply use it for comparison against the new bucket, in order to validate the import procedure.
Additionally, as we intend to follow a gradual rollout for the production registry, with two registry clusters (the existing one and the new one with the database) side by side, each with its own bucket (please see gitlab-org/container-registry#191 (closed) for more details), having two buckets will enable us to replicate the same scenario in pre-production when we're ready to do so.
Requirements
-
Create new GCS bucket in pre-production; -
Existing GCS bucket ( gitlab-pre-registry
) remains intact; -
The application credentials for the new bucket are the same than the old one; -
@jdrpereira
and@hswimelar
have permissions to access both buckets through the GCP UI /gsutil
CLI for debugging purposes.