Halaman ini menjelaskan bagaimana penonaktifan Container Registry yang akan datang, yang dimulai pada 18 Maret 2025, dapat memengaruhi workload Google Kubernetes Engine (GKE). Halaman ini memberikan informasi tentang potensi dampak pada workload Anda dan langkah-langkah migrasi yang direkomendasikan.
Informasi ini ditujukan untuk Admin, arsitek, dan Operator yang menyimpan image container GKE di Container Registry.
Tentang penonaktifan Container Registry
Container Registry tidak digunakan lagi pada 15 Mei 2023 dan akan
dihentikan mulai 18 Maret 2025. Artifact Registry adalah pengganti yang direkomendasikan untuk Container Registry. Artifact Registry menyediakan fitur pengelolaan container yang sama seperti Container Registry, dan mencakup fitur serta manfaat tambahan.
Mulai 18 Maret 2025, Anda tidak akan dapat menulis image ke repositori Container Registry. Mulai 3 Juni 2025, GKE tidak akan dapat membaca image yang Anda simpan di Container Registry. Hal ini dapat menyebabkan gangguan workload.
Sebelum 18 Maret 2025, lakukan transisi repositori Anda dari Container Registry ke Artifact Registry. Untuk mengetahui petunjuknya, lihat
Melakukan transisi dari Container Registry.
Dampak penonaktifan pada workload yang dikelola GKE
Semua beban kerja yang dikelola GKE yang berjalan di node Anda telah
beralih ke Artifact Registry. Artifact Registry mendukung repositori sebagai fitur yang Tersedia Secara Umum.gcr.io Tidak diperlukan tindakan lebih lanjut.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-31 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."]]
