Tidy Windows cluster setup pages

[sftim]

This is a Bug Report

Problem: The Windows in Kubernetes pages are not really a clear guide to setting up a cluster than can run Windows pods.

Proposed Solution:

• Migrate and rename https://kubernetes.io/docs/setup/production-environment/windows/user-guide-windows-containers/
  • I would rename that page to “Run a Pod That Has Windows Containers” and make it be a task
• Migrate the remaining page https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/ to https://kubernetes.io/docs/setup/production-environment/windows-nodes/
  • Optional extra tidying: extract content that's not relevant to cluster setup and move that to new pages within https://kubernetes.io/docs/reference/
• Add redirects accordingly
• Hyperlink from the new page https://kubernetes.io/docs/setup/production-environment/windows-nodes/ to any added reference pages.

Page to Update:
https://kubernetes.io/docs/setup/production-environment/windows/ and child pages

Additional Information:
/language en
/sig windows
/kind cleanup

[sftim]

The new page https://kubernetes.io/docs/setup/production-environment/windows-nodes/ should definitely and prominently hyperlink to https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/

(these pages are not the same, because kubeadm is not the only game in town)

[sftim]

/sig cluster-lifecycle

[mehabhalodiya]

/triage accepted

[sftim]

Relevant to #31428

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

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.