prepare kinder workflows for k/k branch rename

[neolit123]

looks like the k/k branch will be renamed from master to main on august 3rd. edit: 9th ?

https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAOxYG4wipNHR4rAC6SVH8%2BVoQj84Xum%2BTrTRwhsSm3Vjz%3D0KwQ%40mail.gmail.com?utm_medium=email&utm_source=footer

we have to update the source code of https://github.com/kubernetes/kubeadm/tree/main/kinder/ci/tools/update-workflows which hardcodes "master". then run kinder/hack/update-workflows.sh and pr k/test-infra and k/kubeadm.

[neolit123]

looks like it was postponed to 1.26 after discussions

[wangyysde]

cc @wangyysde

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

[SataQiu]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale