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.

Sign up for GitHub

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

Jump to bottom

Migrate to Artifact Registry from Container Registry #1339

Open
NimJay opened this issue Dec 1, 2022 · 3 comments
Open

Migrate to Artifact Registry from Container Registry #1339

NimJay opened this issue Dec 1, 2022 · 3 comments
Assignees
@NimJay
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@NimJay
Copy link
Collaborator

NimJay commented Dec 1, 2022

  • Today, Online Boutique uses Google Cloud's Container Registry for the container images that it published.
  • For instance, gcr.io/google-samples/emailservice:v0.5.0 is hosted on Container Registry.
  • However, Artifact Registry is the recommended way to host container images on Google Cloud — not Container Registry.
  • Relevant documentation: Transition from Container Registry.
  • We should migrate to Artifact Registry.
@NimJay NimJay changed the title Migrate to Artifact Registry Migrate Artifact Registry from Container Registry Dec 1, 2022
@NimJay NimJay changed the title Migrate Artifact Registry from Container Registry Migrate to Artifact Registry from Container Registry Dec 1, 2022
@NimJay NimJay added priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Dec 1, 2022
This was referenced Dec 1, 2022
Closed
Closed
@NimJay
Copy link
Collaborator Author

NimJay commented Feb 22, 2023 •
edited

Update (to cool down our teams' OoSLO list): This work was originally planned for 2023 Q4, but it could be delayed since our team's priorities have changed significantly.

@minherz minherz added priority: p3 Desirable enhancement or fix. May not be included in next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels May 23, 2023
@minherz
Copy link
Contributor

minherz commented May 23, 2023

Priority is decreased because the required migration is not urgent.

@muncus
Copy link
Contributor

muncus commented Nov 16, 2023

This continues to be low-priority work.

@NimJay NimJay added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p3 Desirable enhancement or fix. May not be included in next release. labels Mar 8, 2024
@bourgeoisor bourgeoisor mentioned this issue Apr 17, 2024
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NimJay NimJay

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@muncus @minherz @NimJay