rename the default branch to "main"

[neolit123]

the k8s project is following the new rules of inclusive naming and the default branch of repositories should be renamed from "master" to "main".

steps for repos are outline here:
https://www.kubernetes.dev/resources/rename/

the kubeadm repository surface exposure is fairly limited, since it does not have any importable parts (we assume...at least).

things we have to do as well:

• add neolit123 as admin to be able to perform the default branch rename:
  kubernetes/sig-cluster-lifecycle: update kubeadm teams org#3056
• update the tooling that generates test jobs to use "main" https://github.com/kubernetes/kubeadm/tree/master/kinder/ci/tools/update-workflows
  Update testinfra jobs to use 'main' base_ref #2590
• update references to the master branch (ideally use git.k8s.io/kubeadm instead):
  kubeadm: use git.k8s.io to link to kubeadm repo website#30229
  cluster-lifecycle/kubeadm: update OWNERS URL to use main branch community#6184
• update test infra jobs:
  kubeadm: prepare test jobs for the master->main transition test-infra#24131
• do the actual rename via github UI
• notify the SIG ML:
  https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/D0xXMpVv6xU

[RA489]

/cc

[neolit123]

adding myself as admin here to be able to perform the rename:
kubernetes/org#3056

People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch.

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch

[neolit123]

searching at https://cs.k8s.io/ for kubeadm master branch refs, i cannot seem to find anything else active / not out-of-date.
we have a few outdated design / docs blog posts that are probably not going to be updated to use main regardless.

i think this is good to go.

use this to update your local k/kubeadm clone:

$ git branch -m master main
$ git fetch origin
$ git branch -u origin/main main
$ git remote set-head origin -a

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes

[neolit123]

@kubernetes/owners
hello, we updated tests/docs, renamed the actual branch and notified the SIG ML.
is there anything else that has to be done on your side?

note: the guide here https://www.kubernetes.dev/resources/rename/ says to ping the github team.

EDIT: *.k8s.io/foo might need an update to use main when appropriate - e.g. notice the blue text on top when opening repos that already moved to main:
https://git.k8s.io/kubeadm/OWNERS
https://sigs.k8s.io/cluster-api/OWNERS
^ likely because it uses master and then github redirects to main.

[nikhita]

@kubernetes/owners
hello, we updated tests/docs, renamed the actual branch and notified the SIG ML.
is there anything else that has to be done on your side?

No, everything looks great. Thanks for taking this up!

[nikhita]

Probably unrelated to the branch rename...there's a webhook configured for the kubeadm repo (you should be able to view this with admin access). The webhook deliveries are failing. They look unrelated to the branch rename and have been failing for quite sometime. Might be worth considering removing it? I'm not sure what it's about.

[shivanshuraj1333]

@neolit123 do we've any pending tasks here? I'm happy to contribute if there's any :)

[neolit123]

Probably unrelated to the branch rename...there's a webhook configured for the kubeadm repo

I suspect this is something that happened circa 2017 where a mac app called Ship accidentally installed its hooks automaticaly on all repositories where an authorized github account has admin access.

I will remove the webhook.

https://news.ycombinator.com/item?id=13495216
https://www.realartists.com/docs/2.0/index.html

[neolit123]

@shivanshu1333
Nope. We can close this issue.