add separate task pages for adding Linux/Windows nodes with kubeadm

[neolit123]

follow up on discussions in:

• https://github.com/kubernetes/website/issues/34476

slack:

• https://kubernetes.slack.com/archives/C1J0BPD2M/p1725978983889459

proposed plan for a PR:

• creates the Linux task page by moving / refactoring the existing "join node" contents from the "create a cluster" page: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#join-nodes
• creates the Windows task page by taking the content from https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/guides/guide-for-adding-windows-node.md
• at the end of the Windows page we add note/disclaimer whatever that says that CNI on Windows needs special handling and we link to the various CNI choices at: https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/guides/guide-for-adding-windows-node.md#networking-configuration
• adds tabs in the https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#join-nodes to choose between OS for joining nodes.

note: SIG windows gave +1 on the idea as well during their Zoom meeting on Sept 10th 2024.

/sig cluster-lifecycle docs windows /assign

[neolit123]

/triage accepted

[sftim]

I'm afraid that this seems similar to https://github.com/kubernetes/website/issues/44248

/triage duplicate /remove-triage accepted

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[sftim]

Can we use #44248? I'm sure we'd be happy to revise the description of that existing issue @neolit123.

[neolit123]

assigning myself to the other ticket.

[sftim]

/reopen (momentarily)

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to [this](https://github.com/kubernetes/website/issues/47884#issuecomment-2343609624): >/reopen >(momentarily) Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[sftim]

/close not-planned

[k8s-ci-robot]

@sftim: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/47884#issuecomment-2343609958): >/close not-planned Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.