Container Registry deprecation

Effective May 15, 2023, Container Registry is deprecated and is superseded by Artifact Registry.

We are taking a phased approach to discontinuing Container Registry. After May 15, 2024. Google Cloud projects without previous usage of Container Registry will only support hosting and managing images for the gcr.io domain in Artifact Registry.

This change affects:

  • Newly created projects.
  • Existing projects where you have not pushed an image to Container Registry.

Organizations that have not used Container Registry before January 8, 2024 will have any new gcr.io repositories hosted on Artifact Registry by default.

When you enable the Artifact Registry API in these projects, Artifact Registry will automatically handle creation of gcr.io repositories in Artifact Registry and redirect requests to the gcr.io domain to the appropriate Artifact Registry repository.

Container Registry is still available in projects where either of the following actions occurred before May 15, 2024:

  • You enabled the Container Registry API.
  • You pushed an image to a registry host in the project.

Additional restrictions

After January 8, 2024, organizations that haven't used Container Registry before, and projects that don't belong to organizations will have any new gcr.io repositories hosted on Artifact Registry by default.

Prepare to transition to Artifact Registry

Depending on how you configure and use Container Registry, you might need to perform some configuration steps to prepare a new project to successfully handle requests to the gcr.io domain. For example, principals that access the repositories must have an appropriate Artifact Registry role or a role with equivalent permissions.

We recommend that you:

  • Test and verify your existing Container Registry workflows work with Artifact Registry before May 15, 2024. You can set up gcr.io domain support in a test project to confirm that existing automation and integration with services such as Cloud Build, Google Kubernetes Engine, or Cloud Functions work as expected. If issues occur, you can reroute gcr.io traffic back to Container Registry and make the required changes to address the issue.

  • Transition projects with active Container Registry to Artifact Registry repositories. See Transition from Container Registry to learn about feature differences and transition options.

  • Prepare projects where you are not actively using Container Registry, but expect to set up a registry in the future. See Prepare for gcr.io hosted on Artifact Registry by default.

After the initial phase of Container Registry, we will communicate changes to the service in accordance with the Google Cloud terms of service.