Skip to content
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

Open
steren opened this issue Jun 26, 2023 · 4 comments
Open

Migrate instructions to use Artifact Registry #3298

steren opened this issue Jun 26, 2023 · 4 comments
Labels
api: artifactregistry Issues related to the Artifact Registry API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: docs Improvement to the documentation for an API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@steren
Copy link
Contributor

steren commented Jun 26, 2023

On this page, users are invited to use gcr.io.

These instructions should be updated to use Artifact Registry

@steren steren added priority: p3 Desirable enhancement or fix. May not be included in next release. triage me I really want to be triaged. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Jun 26, 2023
@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Jun 26, 2023
@iennae iennae added the api: artifactregistry Issues related to the Artifact Registry API. label Jun 29, 2023
@RichieEscarez
Copy link

@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?

@kweinmeister kweinmeister added type: docs Improvement to the documentation for an API. and removed samples Issues that are directly related to samples. triage me I really want to be triaged. labels Aug 4, 2023
@RichieEscarez
Copy link

RichieEscarez commented Aug 4, 2023

/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.

@RichieEscarez RichieEscarez removed their assignment Aug 4, 2023
@jama22
Copy link

jama22 commented Aug 4, 2023

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

@pattishin pattishin self-assigned this Mar 5, 2024
@iennae
Copy link
Contributor

iennae commented Apr 17, 2024

@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?

@pattishin pattishin removed their assignment Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: artifactregistry Issues related to the Artifact Registry API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: docs Improvement to the documentation for an API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

6 participants