Stop using Google Container Registry as it's being discontinued

[david-a-wheeler]

We must stop using Google Container Registry as it's being discontinued. Container Registry is being discontinued starting May 15, 2024. Google recommends switching to Artifact Registry instead. Below is more information.

We’re writing to let you know that starting July 19, 2023, we will activate the service artifactregistry.googleapis.com (Artifact Registry) for projects with service dependencies on Container Registry.

What do you need to know?

Container Registry is being discontinued starting May 15, 2024, and replaced by Artifact Registry to provide an enhancement on the capabilities and performance of the platform. New projects with no prior Container Registry usage will store images from dependent services in Artifact Registry instead of Container Registry after May 15, 2024. We are adding Artifact Registry as a dependent service so that services that currently activate Container Registry also automatically activate Artifact Registry.

Services that depend on Container Registry include:

appengine.googleapis.com (App Engine)
appengineflex.googleapis.com (App Engine Flex)
config.googleapis.com (Cloud Config Manager)
cloudbuild.googleapis.com (Cloud Build)
container.googleapis.com (GKE)
visualinspection.googleapis.com (Visual Inspection AI)
run.googleapis.com/runapps.googleapis.com (Cloud Run)
containerscanning.googleapis.com and ondemandscanning.googleapis.com (Container Analysis)
cloudfunctions.googleapis.com (Cloud Functions)
You will not be billed for Artifact Registry until you start using the service.

What do you need to do?

No action is required on your part to add this service. You will receive a separate communication with subject Upgrade to Artifact Registry from Container Registry alongside this announcement, which will provide details on actions you may need to take for the discontinuation of Container Registry.

Your projects that use Container Registry currently are listed below:

allstar-ossf (268889434356)
We’re here to help

Additional details about this transition will also be published in our release notes page.
To learn more about what Artifact Registry offers, see the new feature summary documentation.
We thank you for your patience and understanding as we make this important change.

– The Google Container Registry Team

[Jung47]

Thank @jeffmendoza

[Jung47]

เราต้องหยุดใช้ Google Container Registry เนื่องจากถูกยกเลิก Container Registry จะถูกยกเลิกตั้งแต่วันที่ 15 พฤษภาคม 2024 Google แนะนำให้เปลี่ยนไปใช้ Artifact Registry แทน ด้านล่างนี้เป็นข้อมูลเพิ่มเติม

We’re writing to let you know that starting July 19, 2023, we will activate the service artifactregistry.googleapis.com (Artifact Registry) for projects with service dependencies on Container Registry.

What do you need to know?

Container Registry is being discontinued starting May 15, 2024, and replaced by Artifact Registry to provide an enhancement on the capabilities and performance of the platform. New projects with no prior Container Registry usage will store images from dependent services in Artifact Registry instead of Container Registry after May 15, 2024. We are adding Artifact Registry as a dependent service so that services that currently activate Container Registry also automatically activate Artifact Registry.

Services that depend on Container Registry include:

appengine.googleapis.com (App Engine)
appengineflex.googleapis.com (App Engine Flex)
config.googleapis.com (Cloud Config Manager)
cloudbuild.googleapis.com (Cloud Build)
container.googleapis.com (GKE)
visualinspection.googleapis.com (Visual Inspection AI)
run.googleapis.com/runapps.googleapis.com (Cloud Run)
containerscanning.googleapis.com and ondemandscanning.googleapis.com (Container Analysis)
cloudfunctions.googleapis.com (Cloud Functions)
You will not be billed for Artifact Registry until you start using the service.

What do you need to do?

No action is required on your part to add this service. You will receive a separate communication with subject Upgrade to Artifact Registry from Container Registry alongside this announcement, which will provide details on actions you may need to take for the discontinuation of Container Registry.

Your projects that use Container Registry currently are listed below:

allstar-ossf (268889434356)
We’re here to help

Additional details about this transition will also be published in our release notes page.
To learn more about what Artifact Registry offers, see the new feature summary documentation.
We thank you for your patience and understanding as we make this important change.

– The Google Container Registry Team