Impact of Adding Artifact Registry to Projects Using Container Registry

[bino98]

In our Google Cloud project, we are currently using Docker images stored in Container Registry with Google Kubernetes Engine.

To prepare for the end of support for Container Registry, we are planning to migrate to Artifact Registry. As part of this migration, we have set up a separate Google Cloud project with an infrastructure identical to our production environment in order to validate the migration. However, we found that Container Registry cannot be activated in new projects, which prevents us from confirming the behavior.

I would like to verify the following points:

• In our current project, where we are using Container Registry, would adding an Artifact Registry repository have any negative impact on Container Registry? For example, would access to Container Registry be disrupted, or could any repositories be deleted? Could this lead to changes that would require modifications to our current production setup?
• I understand that Artifact Registry supports both gcr.io domain-based repositories and pkg.dev domain-based repositories. Is it correct to assume that creating either of these repository types will not impact Container Registry in any way?

[greb]

Hi @bino98,

Welcome to Google Cloud Community!

Adding an Artifact Registry repository to your current project will have no detrimental impact on Container Registry or interrupt access to existing gcr.io repositories. Both services can survive without interfering with each other, and repositories will not be destroyed until specifically requested. You may safely create an Artifact Registry repository (gcr.io or pkg.dev-based) without requiring urgent changes to your production configuration.

For reference, Artifact Registry supports both domain-based repositories, and none will interfere with Container Registry's present activities.

I hope the above information is helpful.