This page describes how the upcoming shutdown of Container Registry, which begins on March 18, 2025, might impact Google Kubernetes Engine (GKE) workloads. This page provides information about the potential impact on your workloads and recommended migration steps.

<br />

This information is for Admins and architects and Operators who
store GKE container images in Container Registry.

## About the Container Registry shutdown

Container Registry was deprecated on May 15, 2023 and will be
shut down starting on March 18, 2025. Artifact Registry is the
recommended replacement for Container Registry. Artifact Registry provides
the same container management features as Container Registry, and includes
additional features and benefits.

For details about the shutdown, including the timeline, see
[What happens after March 18, 2025](https://docs.cloud.google.com/artifact-registry/docs/transition/prepare-gcr-shutdown#what-happens-after-shutdown)
in the Artifact Registry documentation.

## Impact of the shutdown on your workloads

Starting on March 18, 2025, you won't be able to write images to
Container Registry repositories. Starting on June 03, 2025,
GKE won't be able to read images that you store in
Container Registry. This might result in workload disruptions.

Before March 18, 2025, transition your repositories from
Container Registry to Artifact Registry. For instructions, see
[Transition from Container Registry](https://docs.cloud.google.com/artifact-registry/docs/transition/transition-from-gcr.md.txt).

## Impact of the shutdown on GKE-managed workloads

All GKE-managed workloads that run in your nodes have already
transitioned to Artifact Registry. Artifact Registry supports `gcr.io`
repositories as a Generally Available feature. No further action is required.