-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Refresh kubeadm docs for Windows #33324
Conversation
/sig windows |
@@ -333,6 +333,10 @@ The nodes are where your workloads (containers and Pods, etc) run. To add new no | |||
kubeadm join --token <token> <control-plane-host>:<control-plane-port> --discovery-token-ca-cert-hash sha256:<hash> | |||
``` | |||
|
|||
{{< note >}} | |||
On Windows you may need to specify the `cri-socket` parameter. For example, with Containerd as the runtime add `--cri-socket "npipe:////./pipe/containerd-containerd"` to the `kubeadm join` command |
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.
When do users not need to specify the cri-socket
parameter for Windows?
If we say may need to
I think we should give guidance on when they would or wouldn't need to specify the extra arg.
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.
Makes sense. I believe it is required for any remote runtimes. If using docker shim then it is not required. Since these docs are for 1.24+ should I be more direct and be more direct that it is requird something like:
On Windows you may need to specify the `cri-socket` parameter. For example, with Containerd as the runtime add `--cri-socket "npipe:////./pipe/containerd-containerd"` to the `kubeadm join` command | |
On Windows when using a remote runtime the `cri-socket` parameter is required. For example when using Containerd as the runtime add `--cri-socket "npipe:////./pipe/containerd-containerd"` to the `kubeadm join` command |
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 think from Tuesday (the expected v1.24 release date), setting a CRI socket path becomes mandatory.
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.
Is this required then?
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.
Maybe we should say:
On Windows you should specify the cri-socket
parameter in the kubeadm join
command. The default path is "npipe:////./pipe/containerd-containerd" for containerd.
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.
updated
content/en/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes.md
Outdated
Show resolved
Hide resolved
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
content/en/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes.md
Outdated
Show resolved
Hide resolved
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.
/hold
Until v1.24 is released, I'd like to avoid provoking merge conflicts for the v1.24 docs branch. This PR touches a doc that was updated in light of the dockershim removal.
OK to unhold after that release.
@@ -333,6 +333,10 @@ The nodes are where your workloads (containers and Pods, etc) run. To add new no | |||
kubeadm join --token <token> <control-plane-host>:<control-plane-port> --discovery-token-ca-cert-hash sha256:<hash> | |||
``` | |||
|
|||
{{< note >}} | |||
On Windows you may need to specify the `cri-socket` parameter. For example, with Containerd as the runtime add `--cri-socket "npipe:////./pipe/containerd-containerd"` to the `kubeadm join` command |
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 think from Tuesday (the expected v1.24 release date), setting a CRI socket path becomes mandatory.
289e095
to
1e032ac
Compare
1e032ac
to
f875adc
Compare
/lgtm |
/assign @onlydole |
/assign @sftim |
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.
If someone visits https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/ then this PR will serve them a 404 response.
Can we redirect them to a different page?
Also, some specific (inline) feedback.
content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes.md
Outdated
Show resolved
Hide resolved
I've updated the docs based on the feedback. Thanks! |
/lgtm |
@jsturtevant could you add the redirect that I mentioned in #33324 (review) ? The file to change is /lgtm cancel |
5be91b0
to
3693d1c
Compare
@sftim sorry about missing that, updated. There were a few other redirects on that file, I left them in place but let me know if they should be consolidated in someway. |
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.
Thanks
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
/lgtm |
LGTM label has been added. Git tree hash: 5a4e6acdf3111856706ac92d9527060d7e5e1394
|
Updates Windows kubeadm documentation:
cri-socket
parameter.This is a follow up from the feedback recieved in #32862 (comment)