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.

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

Update registry k8s.gcr.io -> registry.k8s.io #2103

Merged
merged 1 commit into from
Feb 22, 2023

Conversation

ArkaSaha30
Copy link
Member

What this PR does / why we need it:
This PR will update the uses of deprecating [k8s.gcr.io](http://k8s.gcr.io/) registry to [registry.k8s.io](http://registry.k8s.io/) prior to the planned April freeze.

Which issue this PR fixes(if applicable):
fixes # kubernetes/k8s.io#4738

Special notes for reviewers:
Search results: https://cs.k8s.io/?q=k8s.gcr.io&i=nope&files=&excludeFiles=vendor%2F&repos=kubernetes/cloud-provider-openstack

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 16, 2023
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 16, 2023
@ArkaSaha30 ArkaSaha30 changed the title Update registry k8s.gcr.io -> registry.k8s.io [WIP] Update registry k8s.gcr.io -> registry.k8s.io Feb 16, 2023
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2023
@ArkaSaha30
Copy link
Member Author

/retest-required

@zetaab
Copy link
Member

zetaab commented Feb 17, 2023

@ArkaSaha30 can you rebase your branch against master, it has fixes to CI tests

@ArkaSaha30 ArkaSaha30 force-pushed the migrate-registry branch 2 times, most recently from 23ecfcb to a6faa94 Compare February 17, 2023 06:51
@zetaab
Copy link
Member

zetaab commented Feb 17, 2023

/retest

@ArkaSaha30
Copy link
Member Author

@zetaab the tests are still failing, is it falky? Or should I create a fresh PR and check?

@zetaab
Copy link
Member

zetaab commented Feb 17, 2023

its reported to sig-testing, there are some problems with the serviceaccount tokens

@zetaab
Copy link
Member

zetaab commented Feb 17, 2023

/retest

@jichenjc
Copy link
Contributor

/lgtm

looks like there are some changes that already done #2100
so should we rebase then get this merged?

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 18, 2023
Signed-off-by: ArkaSaha30 <arkasaha30@gmail.com>
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 20, 2023
@ArkaSaha30 ArkaSaha30 changed the title [WIP] Update registry k8s.gcr.io -> registry.k8s.io Update registry k8s.gcr.io -> registry.k8s.io Feb 20, 2023
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 20, 2023
@ArkaSaha30
Copy link
Member Author

Hey @jichenjc, I have rebased with #2100, its good for LGTM

@jichenjc
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 22, 2023
@ArkaSaha30
Copy link
Member Author

Thanks @jichenjc for the quick response, if its all good can you please approve this PR as well?

@jichenjc
Copy link
Contributor

jichenjc commented Feb 22, 2023

/approve

:)

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jichenjc

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 22, 2023
@k8s-ci-robot k8s-ci-robot merged commit 847eadd into kubernetes:master Feb 22, 2023
m-bull pushed a commit to stackhpc/cloud-provider-openstack that referenced this pull request Feb 23, 2023
Signed-off-by: ArkaSaha30 <arkasaha30@gmail.com>
Co-authored-by: Jesse Haka <haka.jesse@gmail.com>
m-bull pushed a commit to stackhpc/cloud-provider-openstack that referenced this pull request Feb 23, 2023
Signed-off-by: ArkaSaha30 <arkasaha30@gmail.com>
Co-authored-by: Jesse Haka <haka.jesse@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants