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.
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.
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, seeTransition from Container Registry.
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 supportsgcr.iorepositories as a Generally Available feature. No further action is required.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Transition from Container Registry to Artifact Registry in GKE\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis 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.\n\n\u003cbr /\u003e\n\nThis information is for Admins and architects and Operators who\nstore GKE container images in Container Registry.\n\nAbout the Container Registry shutdown\n-------------------------------------\n\nContainer Registry was deprecated on May 15, 2023 and will be\nshut down starting on March 18, 2025. Artifact Registry is the\nrecommended replacement for Container Registry. Artifact Registry provides\nthe same container management features as Container Registry, and includes\nadditional features and benefits.\n\nFor details about the shutdown, including the timeline, see\n[What happens after March 18, 2025](/artifact-registry/docs/transition/prepare-gcr-shutdown#what-happens-after-shutdown)\nin the Artifact Registry documentation.\n\nImpact of the shutdown on your workloads\n----------------------------------------\n\nStarting on March 18, 2025, you won't be able to write images to\nContainer Registry repositories. Starting on June 03, 2025,\nGKE won't be able to read images that you store in\nContainer Registry. This might result in workload disruptions.\n\nBefore March 18, 2025, transition your repositories from\nContainer Registry to Artifact Registry. For instructions, see\n[Transition from Container Registry](/artifact-registry/docs/transition/transition-from-gcr).\n\nImpact of the shutdown on GKE-managed workloads\n-----------------------------------------------\n\nAll GKE-managed workloads that run in your nodes have already\ntransitioned to Artifact Registry. Artifact Registry supports `gcr.io`\nrepositories as a Generally Available feature. No further action is required."]]
