Container Registry tidak digunakan lagi. Mulai 18 Maret 2025, Container Registry akan dinonaktifkan dan penulisan image ke Container Registry tidak tersedia. Untuk mengetahui informasi selengkapnya tentang penghentian penggunaan Container Registry dan cara melakukan migrasi ke Artifact Registry, lihat Penghentian penggunaan Container Registry.
Setiap permintaan yang dikirim ke host Container Registry di domain gcr.io memiliki batas waktu tunggu 2 jam.
Ada batas kuota tetap pada permintaan ke host Container Registry.
Batas ini adalah per alamat IP klien.
50.000 permintaan HTTP setiap 10 menit
1.000.000 permintaan HTTP per hari
Agar tidak melebihi batas ini, Anda dapat:
Tingkatkan jumlah alamat IP yang terhubung ke Container Registry.
Tambahkan percobaan ulang yang menyebabkan penundaan. Misalnya, Anda dapat menggunakan
backoff eksponensial.
Jika Anda memerlukan fleksibilitas yang lebih besar, pertimbangkan untuk menggunakan
Artifact Registry
untuk mengelola container, bukan Container Registry. Batas permintaan berada di tingkat project, dan secara default tidak ada batas permintaan per pengguna. Anda juga dapat meminta penambahan kuota untuk Artifact Registry. Untuk mengetahui informasi selengkapnya, lihat dokumentasi
Kuota dan batas untuk Artifact Registry.
Kuota dan batas Cloud Storage
Container Registry menggunakan Cloud Storage untuk setiap penyimpanan yang mendasari registry. Kuota & Batas Cloud Storage berlaku untuk setiap registry.
Kuota Cloud KMS dan Container Registry
Saat Anda menggunakan CMEK di Container Registry, project Anda dapat memakai kuota permintaan kriptografis Cloud KMS.
Misalnya, bucket penyimpanan yang dienkripsi CMEK dapat memakai kuota ini untuk setiap upload atau download.
Operasi enkripsi dan dekripsi menggunakan kunci CMEK memengaruhi kuota Cloud KMS hanya jika Anda menggunakan kunci eksternal (Cloud EKM).
Pastikan Anda memiliki kuota yang cukup untuk mengaktifkan
enkripsi rahasia lapisan aplikasi bagi aplikasi dan alur kerja Anda.
Untuk informasi lebih lanjut, lihat Kuota Cloud KMS.
[[["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-08-19 UTC."],[[["\u003cp\u003eContainer Registry has a 2-hour timeout limit for any request sent to a host in the \u003ccode\u003egcr.io\u003c/code\u003e domain.\u003c/p\u003e\n"],["\u003cp\u003eThere is a fixed quota limit of 50,000 HTTP requests every 10 minutes and 1,000,000 HTTP requests per day for Container Registry hosts, per client IP address.\u003c/p\u003e\n"],["\u003cp\u003eContainer Registry utilizes Cloud Storage for storage, and therefore Cloud Storage quotas and limits apply to each registry.\u003c/p\u003e\n"],["\u003cp\u003eUsing Customer-Managed Encryption Keys (CMEK) in Container Registry can consume Cloud KMS cryptographic request quotas, particularly when using hardware (Cloud HSM) or external (Cloud EKM) keys.\u003c/p\u003e\n"]]],[],null,["# Quotas and limits\n\nThis page describes quotas and limits for Container Registry.\n\nFor more information about quotas, see the [Cloud Quotas documentation](/docs/quotas/overview).\n\nRequest limits\n--------------\n\nAny request sent to a Container Registry host in the `gcr.io` domain has a 2\nhour timeout limit.\n\nThere is a fixed quota limit on requests to Container Registry hosts.\nThis limit is per client IP address.\n\n- 50,000 HTTP requests every 10 minutes\n- 1,000,000 HTTP requests per day\n\nTo avoid exceeding these limits, you can:\n\n- Increase the number of IP addresses that connect to Container Registry.\n- Add retries that introduce a delay. For example, you can use [exponential backoff](/storage/docs/exponential-backoff).\n\nIf you require more flexibility, consider using\n[Artifact Registry](/artifact-registry/docs/transition/transition-from-gcr)\nto manage your containers instead of Container Registry. Requests limits are\nat the project level, and by default there is no per-user request limit. You can\nalso request a quota increase for Artifact Registry. For more information, see the\n[Quotas and limits](/artifact-registry/quotas) documentation for Artifact Registry.\n\nCloud Storage quotas and limits\n-------------------------------\n\nContainer Registry uses Cloud Storage for each registry's\nunderlying storage. [Cloud Storage Quotas \\& Limits](/storage/quotas) apply to\neach registry.\n\n\u003cbr /\u003e\n\n\nCloud KMS quotas and Container Registry\n---------------------------------------\n\n\u003cbr /\u003e\n\nWhen you use CMEK in Container Registry,\nyour projects can consume Cloud KMS cryptographic requests\nquotas.\nFor example, CMEK-encrypted storage buckets\ncan consume these quotas for each upload or download.\n\nEncryption and decryption operations using CMEK keys affect Cloud KMS\nquotas only if you use hardware (Cloud HSM) or external\n(Cloud EKM) keys.\n\n\nConfirm that you have enough quota to enable\napplication-layer secrets encryption for your applications and workflows.\nFor more information, see\n[Cloud KMS quotas](/kms/quotas).\n\nArtifact Analysis quotas\n------------------------\n\nSee [Artifact Analysis quotas and\nlimits](/container-analysis/quotas) for information on scanning usage policies."]]
