knative / knative/test-infra

Migrate to Artifact Registry

Open
#3,005 5 comments 1 reaction 0 assignees View on GitHub
area/gcp lifecycle/frozen priority/backlog
Dominant language
Go
Stars
83
Forks
160
PR merge metrics
No merged PRs in 30d

Description

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`

https://github.com/knative/test-infra/pull/3004 introduces the new repository in to the Prow build images.

Contributor guide

Open the contributing guide

Research direction

Start by locating the service-account permissions, container image references, and repository configuration affected by the gcr.io to us-docker.pkg.dev migration. Review the Artifact Registry transition guide and knative/test-infra#3004. Done means required repositories and roles are configured and the affected build images no longer depend on the old registry.

Written by the indexing model from the issue text.

Assessment

Tech stack
gcp
Domain
cloud, infrastructure
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.