Skip to content

WIP: Move staging repo away from gcr.io #271

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
Closed
wants to merge 1 commit into from
Closed

WIP: Move staging repo away from gcr.io #271

wants to merge 1 commit into from

Conversation

xing-yang
Copy link
Contributor

@xing-yang xing-yang commented Jan 24, 2025 •
edited
Loading

As stated here https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr, gcr Container Registry will be shut down after March 18, 2025. We need to move our staging repo away from gcr.io.

Images on staging repo can be viewed here after we moved over:
https://console.cloud.google.com/artifacts/docker/k8s-staging-sig-storage

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jan 24, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xing-yang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot requested review from gnufied and pohly January 24, 2025 22:02
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 24, 2025
@xing-yang
Copy link
Contributor Author

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jan 24, 2025
@xing-yang
Copy link
Contributor Author

xing-yang commented Jan 25, 2025 •
edited
Loading

@pohly Can you please take a look? What else do we need to change to move away from gcr.io which will be shut down soon? Thanks!

cc @msau42 @jsafrane @BlaineEXE @dims

@xing-yang
Copy link
Contributor Author

/retest

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 27, 2025
@xing-yang xing-yang changed the title WIP: Move staging repo from gcr.io to registry.k8s.io WIP: Move staging repo away from gcr.io Jan 27, 2025
@xing-yang xing-yang mentioned this pull request Jan 27, 2025
Open
@xing-yang
Copy link
Contributor Author

/assign @jsafrane @msau42

@andyzhangx
Copy link
Member

how can I access this site: https://console.cloud.google.com/artifacts/docker/k8s-staging-sig-storage?

You need additional access to the project:  k8s-staging-sig-storage
This could be because you have insufficient permissions to access the resource, or because a Principal Access Boundary policy is blocking your access to the resource.

To request access, contact your project administrator and provide them a copy of the following information:

Troubleshooting info:
  Principal: [email protected]
  Resource: k8s-staging-sig-storage
  Troubleshooting URL: console.cloud.google.com/iam-admin/troubleshooter;permissions=artifactregistry.repositories.list;[email protected];resources=%2F%2Fcloudresourcemanager.googleapis.com%2Fprojects%2Fk8s-staging-sig-storage/result

Missing permissions:
  artifactregistry.repositories.list
If your administrator is unable to help, then [contact support ](https://cloud.google.com/support/docs/customer-care-procedures#create_a_support_case).

@k8s-triage-robot
Copy link

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2025
@k8s-triage-robot
Copy link

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@xing-yang
Copy link
Contributor Author

Closing this PR. Will work with sig-k8s-infra on this migration: https://kubernetes.slack.com/archives/CCK68P2Q2/p1738185784348279

@xing-yang xing-yang closed this May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gnufied gnufied Awaiting requested review from gnufied

@pohly pohly Awaiting requested review from pohly

Assignees

@jsafrane jsafrane

@msau42 msau42

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@xing-yang @k8s-ci-robot @andyzhangx @k8s-triage-robot @jsafrane @msau42