-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows documentation overhaul #33582
Windows documentation overhaul #33582
Conversation
/cc @brasmith-ms |
@marosset: GitHub didn't allow me to request PR reviews from the following users: brasmith-ms. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
ac81afe
to
babc202
Compare
content/en/docs/concepts/services-networking/dns-pod-service.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/dns-pod-service.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/dns-pod-service.md
Outdated
Show resolved
Hide resolved
qualified has failed | ||
On Windows, you can only have 1 DNS suffix, which is the DNS suffix associated with that | ||
pod's namespace (mydns.svc.cluster.local for example). Windows can resolve FQDNs | ||
and services or names resolvable with just that suffix. For example, a pod spawned |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Windows can resolve FQDNs and services or names resolvable with just that suffix."
This sentence is difficult to parse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to make this less confusing. Let me know if it makes more sense.
content/en/docs/concepts/services-networking/dns-pod-service.md
Outdated
Show resolved
Hide resolved
* A kubelet running on a Windows node does not have memory | ||
restrictions. `--kubelet-reserve` and `--system-reserve` do not set limits on | ||
kubelet or processes running on the host. This means kubelet or a process on the host | ||
could cause memory resource starvation outside the node-allocatable and scheduler. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
“This means kubelet or a process on the host could cause memory resource starvation outside the node-allocatable and scheduler.”
This sentence is difficult to parse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm for sig-windows, The initial plan is move these files with minimal changes to the correct content locations to make edits to them easier and make the Windows Introduction page easier to manage and comprehend.
Kubernetes on Windows does not support single-stack "IPv6-only" networking. However, | ||
dual-stack IPv4/IPv6 networking for pods and nodes with single-family services | ||
is supported. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@daschott could you help parse the intent of the paragraph? This was a straight copy of https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#ipv6-networking.
I think the plan was to mostly move things as is in this first iteration but this one is pretty confusing. Another thing missing here is what version of Windows is required. WS2019 does not support dual-stack. It is available in 20H2 and WS2022.
content/en/docs/concepts/services-networking/windows-networking.md
Outdated
Show resolved
Hide resolved
@tengqm I have incorporated all of the suggested edits. |
- Move FlexVolume plugins section to docs/concepts/storage/volumes.md - Move CSI plugins section to en/docs/concepts/storage/volumes.md - Move in-tree plugins section to en/docs/concepts/storage/volumes.md
/docs/setup/production-environment/windows to various locations - Moving windows DNS limitations to/docs/concepts/services-networking/dns-pod-service.md - Moving windows session sticky time disclaimer to /docs/concepts/services-networking/service.md - Moving windows dual stack support info to /docs/concepts/services-networking/dual-stack.md - Moving generic Windows content to /docs/concepts/services-networking/windows-networking.md Signed-off-by: Mark Rossetti <[email protected]>
…ster/ Signed-off-by: Mark Rossetti <[email protected]>
…ment/ Signed-off-by: Mark Rossetti <[email protected]>
e711b4e
to
2d955bb
Compare
Sure. I'm okay with whichever approach to improve these pages, provided that the ball is not dropped. |
Understood. |
I'm okay to move this forward. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm cancel
There's one place where this needs a fix.
======= | ||
The scheduler does not use the value of `.spec.os.name` when assigning Pods to nodes. | ||
You should use normal Kubernetes mechanisms for | ||
[assigning pods to nodes](/docs/concepts/scheduling-eviction/assign-pod-node/) | ||
to ensure that the control plane for your cluster places pods onto nodes that are running the | ||
appropriate operating system. | ||
{{< /note >}} | ||
>>>>>>> Moving windows containers user guide out of /setup/production-environment/:content/en/docs/concepts/windows/user-guide.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a broken merge that needs tidying.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, I'll scan the rest of the PR again now too.
…nvironment/ Signed-off-by: Mark Rossetti <[email protected]>
2d955bb
to
70206d9
Compare
/lgtm |
LGTM label has been added. Git tree hash: 90cd4e8c0493f2ae84dd933577bd48df20f7ca75
|
This PR moves all content out of /docs/setup/production-environment/windows to new locations.
Where possible we merged Windows information into the existing docs.
This is a big PR but most of the contents have already been reviewed
I was initially hoping to get all of these changes in with the 1.24 release branch but in order to ease pressure on the release team we all decided to merge these changes after the 1.24 release.
Part of #31428
/label refactor
/sig windows
/assign @jsturtevant @sftim
/cc @tengqm @aravindhp @nate-double-u