-
Notifications
You must be signed in to change notification settings - Fork 166
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
[2025-03-18] Upgrade to Artifact Registry #3768
Comments
@trivikr do you know what the project uses gcr.io for right now? |
The metrics stuff running on GCP is all running on containers on gcr.io. We appear to be missing documentation and/or automation on how to rebuild/update/upload the containers. |
@richardlau is that everything? Just wanted to be sure there was nothing beyond the metrics stuff. |
AFAIK |
When I looked at GCP Container registry for errors as part of debugging download stats in #3697, I verified that they contain docker images for only running metrics stuff as Richard mentioned.
That's right. I posted GCP docs for Container Registry in Node.js 20 upgrade PR in #3767 (comment), and GCP Artifact Registry docs in this issue description to follow whenever migration is prioritized. |
Is your feature request related to a problem? Please describe.
Container Registry is deprecated and scheduled for shutdown on 2025-03-18.
Google Cloud recommends upgrading to Artifact Registry: https://cloud.google.com/artifact-registry/docs/transition/prepare-gcr-shutdown
The nodejs-org project uses Container Registry
Describe the solution you'd like
Follow guide for Set up repositories with gcr.io domain support https://cloud.google.com/artifact-registry/docs/transition/setup-gcr-repo
Additional context
Refs: #3697 (comment)
The text was updated successfully, but these errors were encountered: