Skip to content

Migrate away from GCR #3810

New issue
New issue
Closed
Closed
Migrate away from GCR#3810
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectkind/featureCategorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.sig/releaseCategorizes an issue or PR as relevant to SIG Release.
@ameukam

Description

@ameukam
ameukam
opened on Oct 22, 2024

What would you like to be added:

Part of:

Migrate exiting GCR container registries used for the release process to GCP Artifact registry.

Why is this needed:

GCR will be shutdown in 2025:

March 18, 2025: You will no longer be able to push new images to the Container Registry.
April 22, 2025: You will lose access to existing images in the Container Registry. To maintain access, you must copy them to the Artifact Registry before this date.
May 22, 2025: All requests to the gcr.io domain will be handled exclusively by Artifact Registry. Ensure the Artifact Registry API is enabled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/release-engIssues or PRs related to the Release Engineering subprojectkind/featureCategorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.sig/releaseCategorizes an issue or PR as relevant to SIG Release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions