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

Rename default branch for kubernetes/k8s.io #1597

Closed
spiffxp opened this issue Jan 29, 2021 · 31 comments
Closed

Rename default branch for kubernetes/k8s.io #1597

spiffxp opened this issue Jan 29, 2021 · 31 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Milestone

Comments

@spiffxp
Copy link
Member

spiffxp commented Jan 29, 2021

Part of umbrella issue kubernetes/org#2222

Issue to spec out and then run through renaming the default branch for this repository

  • update pre/postsubmits to trigger on old branch name and new branch name
  • determine whether periodics use default branch or have name hardcoded in git commands
    • if hardcoded, does attempting to checkout old name break?
  • determine whether branch name is part of any job names
  • determine if any docs need to be updated
  • send notice
  • rename branch (ref: https://github.com/github/renaming#renaming-existing-branches)
  • if necessary, update periodics to refer to new branch name
  • if necessary, rename jobs
  • update branch protection config
  • update jobs to only trigger on new branch name
  • make sure things still work
    • keep an eye on ci and prs for a bit
    • trial the local development experience with pre-rename clone
  • send notice

/sig contributor-experience
/area github-management
trialing a repo for this subproject
/wg k8s-infra
owns this repo
/sig testing
to discover any prow issues
/milestone v1.21
/priority important-soon
/assign @spiffxp
I plan on speccing this out, whether/when to execute depends on how kubernetes/org goes

@k8s-ci-robot k8s-ci-robot added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. wg/k8s-infra labels Jan 29, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jan 29, 2021
@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 29, 2021
@k8s-ci-robot
Copy link
Contributor

@spiffxp: The label(s) area/github-management cannot be applied, because the repository doesn't have them

In response to this:

Issue to spec out and then run through renaming the default branch for this repository

  • update pre/postsubmits to trigger on old branch name and new branch name
  • determine whether periodics use default branch or have name hardcoded in git commands
  • if hardcoded, does attempting to checkout old name break?
  • determine whether branch name is part of any job names
  • determine if any docs need to be updated
  • send notice
  • rename branch (ref: https://github.com/github/renaming#renaming-existing-branches)
  • if necessary, update periodics to refer to new branch name
  • if necessary, rename jobs
  • update branch protection config
  • update jobs to only trigger on new branch name
  • make sure things still work
  • keep an eye on ci and prs for a bit
  • trial the local development experience with pre-rename clone
  • send notice

/sig contributor-experience
/area github-management
trialing a repo for this subproject
/wg k8s-infra
owns this repo
/sig testing
to discover any prow issues
/milestone v1.21
/priority important-soon
/assign @spiffxp
I plan on speccing this out, whether/when to execute depends on how kubernetes/org goes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@spiffxp
Copy link
Member Author

spiffxp commented Jan 29, 2021

PR up for job config changes + prow config changes: kubernetes/test-infra#20675 (holding merge until next week, and completion of the below review)

Still need to:

  • review the code in k8s.io to confirm whether it explicitly references the master branch...
  • review docs to see whether master is explicitly references (beyond uris that github will redirect for us)

@spiffxp
Copy link
Member Author

spiffxp commented Feb 9, 2021

Merged kubernetes/test-infra#20675

@spiffxp
Copy link
Member Author

spiffxp commented Feb 9, 2021

Renamed the branch

@spiffxp
Copy link
Member Author

spiffxp commented Feb 9, 2021

Will leave as-is and cleanup tomorrow

Confirmed:

Known issues:

@spiffxp
Copy link
Member Author

spiffxp commented Feb 18, 2021

https://kubernetes.slack.com/archives/C1TU9EB9S/p1613578896224800 - @xmudrii noticed cs.k8s.io wasn't able to search this repo anymore, @dims enabled detect-ref and we're searchable again

@spiffxp
Copy link
Member Author

spiffxp commented Feb 18, 2021

I'm going to assume the jobs that have no recent runs are fine given everything else worked

@spiffxp
Copy link
Member Author

spiffxp commented Feb 18, 2021

Looking for references to master within this repo:

  • I think we have cip-auditor in cloud run hardcoded to look at master, see
    --update-env-vars="CIP_AUDIT_MANIFEST_REPO_URL=https://github.com/kubernetes/k8s.io,CIP_AUDIT_MANIFEST_REPO_BRANCH=master,CIP_AUDIT_MANIFEST_REPO_MANIFEST_DIR=k8s.gcr.io,CIP_AUDIT_GCP_PROJECT_ID=k8s-artifacts-prod" \
    • but also, looking at logs for it, I see a lot of 500's, I think something else is broken with it
    • manually deployed a new revision with the new branch name Screen Shot 2021-02-17 at 7 42 40 PM
  • dns/octodns-docker/cloudbuild.yaml has 'master' as a default
  • there are some links to k8s.io.*master (github would redirect those anyway, but we can clean them up)

@spiffxp
Copy link
Member Author

spiffxp commented Mar 4, 2021

Still need to cleanup references to master in this repo

Blocking

Nice to have

1 I would like to learn how to deploy k8s.io, but it may be a while before I can get there.

@spiffxp
Copy link
Member Author

spiffxp commented Mar 17, 2021

@nikhita and @dims have helped land some of the necessary changes, edited above comment into checklist and crossed out what's been done

@ameukam
Copy link
Member

ameukam commented Apr 15, 2021

/milestone v1.22

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.21, v1.22 Apr 15, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jun 30, 2021

/help

We could use some help closing out "clean up links to k8s.io/(blob|tree)/master" above. A PR per repo would be fine

List generated via:

curl -s -X POST \
  -F "q=/k8s.io/(tree|blob)/master/" \
  -F "repos=*" \
  "https://cs.k8s.io/api/v1/search" \
| jq -r '.Results | keys | .[]' \
| sort \
| sed -e 's/^/- [ ] /g'

EDIT: updated as of 2021-09-15

  • kubernetes-csi/csi-driver-host-path
  • kubernetes-csi/csi-driver-iscsi
  • kubernetes-csi/csi-driver-nfs
  • kubernetes-csi/csi-lib-utils
  • kubernetes-csi/csi-proxy
  • kubernetes-csi/csi-release-tools
  • kubernetes-csi/csi-test
  • kubernetes-csi/external-attacher
  • kubernetes-csi/external-health-monitor
  • kubernetes-csi/external-provisioner
  • kubernetes-csi/external-resizer
  • kubernetes-csi/external-snapshotter
  • kubernetes-csi/livenessprobe
  • kubernetes-csi/node-driver-registrar
  • kubernetes-csi/volume-data-source-validator
  • kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm
  • kubernetes-sigs/cluster-api-provider-aws
  • kubernetes-sigs/cluster-api-provider-digitalocean
  • kubernetes-sigs/cluster-api-provider-openstack
  • kubernetes-sigs/descheduler
  • kubernetes-sigs/gcp-compute-persistent-disk-csi-driver
  • kubernetes-sigs/gcp-filestore-csi-driver
  • kubernetes-sigs/k8s-container-image-promoter
  • kubernetes-sigs/lwkd (docs: follow kubernetes/k8s.io branch rename: kubernetes-sigs/lwkd#117)
  • kubernetes-sigs/metrics-server
  • kubernetes-sigs/nfs-ganesha-server-and-external-provisioner (Rename master to main kubernetes-sigs/nfs-ganesha-server-and-external-provisioner#55)
  • kubernetes-sigs/nfs-subdir-external-provisioner (Rename master to main kubernetes-sigs/nfs-subdir-external-provisioner#117)
  • kubernetes-sigs/prometheus-adapter (docs: follow kubernetes/k8s.io branch rename: kubernetes-sigs/prometheus-adapter#454)
  • kubernetes-sigs/scheduler-plugins
  • kubernetes-sigs/secrets-store-csi-driver
  • kubernetes/community
  • kubernetes/dns
  • kubernetes/ingress-nginx
  • kubernetes/k8s.io
  • kubernetes/kubernetes
  • kubernetes/perf-tests
  • kubernetes/publishing-bot
  • kubernetes/sig-release
  • kubernetes/test-infra
  • kubernetes/website

@k8s-ci-robot
Copy link
Contributor

@spiffxp:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

We could use some help closing out "clean up links to k8s.io/(blob|tree)/master" above. A PR per repo would be fine

List generated via:

curl -s -X POST \
 -F "q=/k8s.io/(tree|blob)/master/" \
 -F "repos=*" \
 "https://cs.k8s.io/api/v1/search" \
| jq -r '.Results | keys | .[]' \
| sort \
| sed -e 's/^/- [ ] /g'
  • kubernetes-csi/csi-driver-host-path
  • kubernetes-csi/csi-driver-iscsi
  • kubernetes-csi/csi-driver-nfs
  • kubernetes-csi/csi-lib-utils
  • kubernetes-csi/csi-proxy
  • kubernetes-csi/csi-release-tools
  • kubernetes-csi/csi-test
  • kubernetes-csi/external-attacher
  • kubernetes-csi/external-health-monitor
  • kubernetes-csi/external-provisioner
  • kubernetes-csi/external-resizer
  • kubernetes-csi/external-snapshotter
  • kubernetes-csi/livenessprobe
  • kubernetes-csi/node-driver-registrar
  • kubernetes-csi/volume-data-source-validator
  • kubernetes-sigs/cluster-api-bootstrap-provider-kubeadm
  • kubernetes-sigs/cluster-api-provider-aws
  • kubernetes-sigs/cluster-api-provider-digitalocean
  • kubernetes-sigs/cluster-api-provider-openstack
  • kubernetes-sigs/descheduler
  • kubernetes-sigs/gcp-compute-persistent-disk-csi-driver
  • kubernetes-sigs/gcp-filestore-csi-driver
  • kubernetes-sigs/k8s-container-image-promoter
  • kubernetes-sigs/metrics-server
  • kubernetes-sigs/nfs-ganesha-server-and-external-provisioner
  • kubernetes-sigs/nfs-subdir-external-provisioner
  • kubernetes-sigs/scheduler-plugins
  • kubernetes-sigs/secrets-store-csi-driver
  • kubernetes/community
  • kubernetes/dns
  • kubernetes/ingress-nginx
  • kubernetes/k8s.io
  • kubernetes/kubernetes
  • kubernetes/perf-tests
  • kubernetes/publishing-bot
  • kubernetes/sig-release
  • kubernetes/test-infra
  • kubernetes/website

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 30, 2021
@praveenghuge
Copy link

/assign

@anubha-v-ardhan
Copy link
Member

anubha-v-ardhan commented Jul 1, 2021

Closed all my PRs except kubernetes-csi/csi-release-tools#164
as stated in this comment kubernetes-csi/csi-release-tools#164 (comment)

Seems like we have a way to mass update all the repos

@spiffxp
Copy link
Member Author

spiffxp commented Jul 2, 2021

/assign @anubha-v-ardhan @praveenghuge @RinkiyaKeDad
Thank you for taking this on! I've updated #1597 (comment) based on latest results

Sounds like @pohly will help out with the remainder of the kubernetes-csi repos

@RinkiyaKeDad
Copy link
Member

All the PRs for kubernetes/ have now been merged @spiffxp. Please let us know if there is something else we could help with :D

@spiffxp
Copy link
Member Author

spiffxp commented Jul 27, 2021

I refreshed #1597 (comment) and poked the open PRs I could find. There are still some outstanding repos I couldn't find a linked repo for.

Leaving this in v1.22 because it may be basically done if we can figure out how many repos are blocked by the "csi tools will be copied" reasoning

@pohly
Copy link
Contributor

pohly commented Aug 2, 2021

As I mentioned in kubernetes-sigs/nfs-ganesha-server-and-external-provisioner#55 (comment), repo owner are not blocked and can update their copy of csi-release-tools.

@spiffxp
Copy link
Member Author

spiffxp commented Aug 2, 2021

/milestone v1.23

@RinkiyaKeDad
Copy link
Member

Unassinging myself for the moment, but please let me know if there's something that needs help :)

/unassign

@spiffxp
Copy link
Member Author

spiffxp commented Sep 15, 2021

@spiffxp
Copy link
Member Author

spiffxp commented Sep 20, 2021

Hopefully the last bit needed:

@spiffxp
Copy link
Member Author

spiffxp commented Sep 24, 2021

/close
And we're done!

Thanks for the help @RinkiyaKeDad @anubha-v-ardhan @pohly @wongma7 @ikarldasan @praveenghuge

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Closing this issue.

In response to this:

/close
And we're done!

Thanks for the help @RinkiyaKeDad @anubha-v-ardhan @pohly @wongma7 @ikarldasan @praveenghuge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Development

No branches or pull requests

7 participants