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 #3005

Open
upodroid opened this issue Jan 13, 2022 · 5 comments
Open

Migrate to Artifact Registry #3005

upodroid opened this issue Jan 13, 2022 · 5 comments
Labels
area/gcp Issues or PRs related to Google Cloud Infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@upodroid
Copy link
Member

upodroid commented Jan 13, 2022 •
edited
Loading

Google Container Registry has been recommending migrating to Artifact Registry for some time now.

https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr

In theory, this should be straight forward:

  • Ensure all service accounts have been granted Artifact Registry roles
  • One major change is that repositories need to be created.
  • Authentication methods are still the same.

gcr.io will be replaced by us-docker.pkg.dev

#3004 introduces the new repository in to the Prow build images.
@chizhg
Copy link
Member

chizhg commented Jan 13, 2022

Thanks for opening this!

@upodroid upodroid moved this to Needs Design in Infra (Productivity) Feb 10, 2022
@chizhg chizhg moved this from Needs Design to In Design/Discussion in Infra (Productivity) Apr 7, 2022
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 14, 2022
@chizhg
Copy link
Member

chizhg commented Apr 19, 2022

/lifecycle frozen

@knative-prow knative-prow bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 19, 2022
@upodroid upodroid moved this from In Design/Discussion to Blocked in Infra (Productivity) Jun 7, 2022
@upodroid upodroid added area/gcp Issues or PRs related to Google Cloud Infrastructure priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jun 7, 2022
@dprotaso
Copy link
Member

Hey @upodroid is #3004 the only thing we need to do here?

cc @kvmware

@upodroid
Copy link
Member Author

upodroid commented Aug 25, 2023 •
edited
Loading

So #3004 configures the docker cred helper. We need to change the KO_DOCKER_REPO env value to use Artifact Registry and I haven't investigated that work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/gcp Issues or PRs related to Google Cloud Infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
Infra (Productivity)
Status: Blocked
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dprotaso @chizhg @upodroid