Upgrade to Artifact Registry from Container Registry before May 15, 2024

[liliya_borisova]

Hi Google Cloud Community,

I recently received an email from Google Cloud that I need to upgrade to Artifact Registry from Container Registry.

I am not really familiar with Container Registry and Artifact Registry; I am a marketer and use Google Cloud for the sole purpose of running an App Engine project for Server Side website tracking via Google Tag Manager. I don't intend to create any other projects at this point.

Do you have any idea whether or not I need to take any action on my current project?

You help would be highly appreciated.

[Marramirez]

Greetings @liliya_borisova,

Welcome to the Google Cloud Community!

This blog should help you know more about the two registries: Artifact Registry: The next generation of Container Registry

Artifact Registry extends the existing capabilities of the Container Registry. This Feature Comparison contains the differences between the two. While Container Registry will still be available, new features will only be available in Artifact Registry, and Container Registry will only receive critical security fixes. See Container Registry Deprecation.

If you wish to upgrade to Artifact Registry, you can follow this documentation: Transition Container Registry. 

You can also contact Google Cloud Support to help you with your transition from Container Registry to Artifact Registry. Let me know if it helped, thanks!

[camb01x]

Hello @Marramirez 

I am in the same situation as the poster. Currently, I have deployed server side GTM from Google tag manager. This created the container on Google Cloud which we currently have running. It was not a difficult for someone that is not too technical.

However, this is a bit too technical for me but I wanted to check something with you.

For our use case, do you recommend going with "Set up repositories with gcr.io domain support"  or "Transition to standard repositories"?

Thanks!