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

Availability of a Container Image on Google Artifact Registry #2211

Open
trietsch opened this issue May 13, 2024 · 2 comments
Open

Availability of a Container Image on Google Artifact Registry #2211

trietsch opened this issue May 13, 2024 · 2 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern. type: docs Improvement to the documentation for an API.

Comments

@trietsch
Copy link

trietsch commented May 13, 2024

Question

Since Google Container Registry is deprecated in favor of Google Artifact Registry, I was wondering if there are plans to create a container image on one of the pkg.dev domains. As these images might fall under the public images that Google Cloud maintains, this could also be relevant for this question I asked a while ago on StackOverflow.
I can't find anything related in issues (open or closed) or in the readme.

Code

No response

Additional Details

No response

@trietsch trietsch added the type: question Request for information or clarification. label May 13, 2024
@jackwotherspoon
Copy link
Collaborator

@trietsch our container repositories are actually already in Artifact Registry. For naming sake we just kept our container names the same when we migrated. So even though the repo names have gcr.io at the beginning it actually is being hosted in artifact registry.

Example: If you go to gcr.io/cloud-sql-connectors/cloud-sql-proxy you will see it brings you to artifact registry.

I will discuss with the team whether or not we want to use pkg.dev domains to make this less confusing to users.

@trietsch
Copy link
Author

Hey @jackwotherspoon, thanks for the quick reply! I did see something like that in the docs regarding the migration, that GCR registries can be hosted by Artifact Registry, but good to know that they are already migrated.

@enocom enocom added priority: p2 Moderately-important priority. Fix may not be included in next release. type: docs Improvement to the documentation for an API. type: cleanup An internal cleanup or hygiene concern. and removed type: question Request for information or clarification. labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern. type: docs Improvement to the documentation for an API.
Projects
None yet
Development

No branches or pull requests

3 participants