-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate instructions to use Artifact Registry #3298
Comments
@jama22 , that Cloud Run page mentions both Artifact Registry and also GCR but in the context of buildpacks. Will buildpacks move to AR or do we need to continue using the GCR URL locations? |
/assign @jama22 The GCR reference is here in the page: https://cloud.google.com/run/docs/deploying-source-code#limits "Deploying from source with Google Cloud's buildpacks always uses gcr.io/buildpacks/builder:latest." If buildpacks are to remain in GCR, then this issue can be closed because the page otherwise uses Artifact Registry. |
we have some plans to get an AR reigstry address for that builder, so we can leave this issue open and I'll make a PR to update when we have that address available |
@jama22 as of May 15, 2024 Artifact Registry will host images for the gcr.io domain by default. When I look up gcr.io/buildpacks/builder:latest it still looks like it's using Container Registry. Do we know the plan/impact for this? |
On this page, users are invited to use gcr.io.
These instructions should be updated to use Artifact Registry
The text was updated successfully, but these errors were encountered: