GCR to Artifact Registry tracking

[jimangel]

Tracking issue for moving from Google Container Registry to Google Artifact Registry.

Artifact Registry is "The next generation of Container Registry. Store, manage, and secure your build artifacts." Once Artifact Registry graduates from beta, there will be a minimum of 6 months supported on GCR.

The general impact is: us.gcr.io/my-project/webapp becomes us-docker.pkg.dev/my-project/team1/webapp

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

/cc @kubernetes/release-managers @spiffxp @dims @bartsmykla
/priority important-soon
/area artifacts
/sig release
/sig testing
/sig k8s-infra

Update (@ameukam):
Sucess criteria:

• Migrate gcr.io/k8s-artifacts-prod to Artifact Registry
• Migrate staging registries to Artifact Registry

[spiffxp]

Looks like this first went beta in March 2020: https://cloud.google.com/artifact-registry/docs/release-notes#March_16_2020

I'm not inclined to suggest we move on this until at least "Container Analysis and vulnerability scanning" is available: https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr#feature-availability

I would like to understand if k8s.gcr.io already is or can become one of the backwards compatible repos mentioned here: https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr#compatibility

We should consider whether container-image-promoter and any related scripts would need to be rewritten to support new APIs / commands: https://cloud.google.com/artifact-registry/docs/transition/setup-repo#gcloud-comparison

FYI @listx

[ameukam]

ICYMI, Artifact Registry is now GA: https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr#feature-availability

[dims]

Update from @saschagrunert : "We have a research topic on our board about "Support for Google Artifact Registry and how do we transition?"" ( from https://kubernetes.slack.com/archives/C2C40FMNF/p1610377375328600 )

[justaugustus]

This will be part of SIG Release's Artifact Mgmt epic, which I'll be working to flesh out this cycle.

ref: kubernetes/sig-release#1372
/assign
/milestone v1.21

[spiffxp]

I notice the language on https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr#top_of_page has changed from "minimum 6 months of GCR support post-GA" to "Both services will continue to co-exist after Artifact Registry becomes generally available" so I feel like there is less urgency to this

/remove-priority important-soon
/priority important-longterm

[dims]

@spiffxp Whew!!!! thanks.

[spiffxp]

I think we're having problems using docker buildx build to push to GCR (kubernetes/test-infra#20884 (comment)) due to a containerd bug. GCR's not the only service impacted by the bug, but other services seem to have rolled out a workaround by now (including GAR?).

I'm not saying this is impetus enough to migrate now but may be a sign that GCR is headed toward some kind of maintenance mode vs. getting fixes.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[ameukam]

/remove-lifecycle rotten
/lifecycle frozen

[spiffxp]

/remove-priority important-longterm
/priority awaiting-more-evidence

[ameukam]

/milestone v1.30

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dims]

/remove-lifecycle stale

[ameukam]

/milestone v1.32

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ameukam]

/remove-lifecycle stale
/milestone v1.33