Use new upstream for generating reference doc for kubeadm

[tengqm]

According to

• moving kubeadm out of kubernetes/kubernetes
• KEP 1425

we are supposed to use the kubernetes/kubeadm repo as the upstream for reference code generation.

[neolit123]

thanks for logging the ticket. i will keep in touch with #sig-docs once we are ready to take action on this change.

/sig docs cluster-lifecycle /assign

[neolit123]

@tengqm hi, after discussions with SIG Release, and due to some complications related to the k/release repo tooling, we are delaying the move to the k/kubeadm repository for the release of 1.19.

[tengqm]

@neolit123 Thanks for the info.

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

[neolit123]

we are delaying the move to the k/kubeadm repository for the release of 1.19.

...and after more discussions we still haven't landed an agreement on how to proceed for this item. /lifecycle frozen

i have linked this issue in https://github.com/kubernetes/kubeadm/issues/1949 so i'm going to update it when this is actually going to happen.