We migrated from google cloud container registry to Artifact Registry suggested by google. We use this link for migration . So in the Artifact Registry the repository names are similar to container registry. Like gcr.io, us.gcr.io.
In the web app Cloud build yaml file the path needs any changes?
- name: 'gcr.io/cloud-builders/docker' args: ['push', 'us.gcr.io/$PROJECT_ID/appointsd:$_TAG']
Please advise on this.
We migrated from google cloud container registry to Artifact Registry suggested by google. We use this link for migration https://cloud.google/artifact-registry/docs/transition/auto-migrate-gcr-ar. So in the Artifact Registry the repository names are similar to container registry. Like gcr.io, us.gcr.io.
In the web app Cloud build yaml file the path needs any changes?
- name: 'gcr.io/cloud-builders/docker' args: ['push', 'us.gcr.io/$PROJECT_ID/appointsd:$_TAG']
Please advise on this.
Share Improve this question asked Mar 15 at 12:11 vinoth87vinoth87 3101 gold badge2 silver badges17 bronze badges 1- Hi @vinoth87 I have provided an answer below. Please check and let me know if the below suggestions were helpful – Sathi Aiswarya Commented Mar 19 at 13:41
1 Answer
Reset to default 0All requests to the gcr.io domain will be handled exclusively by Artifact Registry. You don't need a new gcr.io path. The gcr.io path will continue to work and automatically convert to Artifact Registry.
As stated in this documentation
Artifact Registry
gcr.iorepositories.gcr.iorepositories let Container Registry users maintain their existing Google Cloud infrastructure by storing container images in Artifact Registry and supporting requests to the samegcr.ioURLs used by Container Registry.
gcr.iorepositories hosted on Artifact Registry are a Generally Available feature, and they will continue to work after the Container Registry deprecation.
For more information on the gcr.io domain, review this documentation