-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
kubeadm: add task pages for adding Linux and Windows worker nodes #47888
kubeadm: add task pages for adding Linux and Windows worker nodes #47888
Conversation
/assign @sftim @divya-mohan0209 /sig cluster-lifecycle windows docs NOTE: i won't be able to work on this next week, but any feedback will be adjusted after that in case the PR doesn't merge this week... |
/hold |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Here's a partial review. I don't have a Windows licence to check out the Windows part.
content/en/docs/tasks/administer-cluster/kubeadm/adding-linux-nodes.md
Outdated
Show resolved
Hide resolved
following commands on the control plane node: | ||
|
||
```bash | ||
openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | \ |
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.
openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | \ | |
# Run this on a control plane node | |
sudo cat /etc/kubernetes/pki/ca.crt | openssl x509 -pubkey | openssl rsa -pubin -outform der 2>/dev/null | \ |
(least privilege)
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, minus the # Run this on a control plane node
part. that is already in the prev sentence.
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.
It doesn't block a merge, but experience confidently shows us that people don't read documentation and many people paste the commands in without reading the text in between.
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.
well, it will fail on a joining worker since the ca.crt doens't exist yet.
so then they will go back and read the prev sentence.
content/en/docs/tasks/administer-cluster/kubeadm/adding-linux-nodes.md
Outdated
Show resolved
Hide resolved
By default, tokens expire after 24 hours. If you are joining a node to the cluster after the current token has expired. You can create a new token by running the following command on the control plane node: | ||
|
||
```bash | ||
kubeadm token create |
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.
kubeadm token create | |
# Run this on a control plane node | |
sudo kubeadm token create |
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, minus # Run this on a control plane node
. the prev sentence already mentions ...running the following command on the control plane node
content/en/docs/tasks/administer-cluster/kubeadm/adding-linux-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
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.
Some thoughts on the Windows part
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
when run on the control plane node. | ||
|
||
Install kubectl for windows (optional) | ||
For more information about it : https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/ |
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.
(at some point) make this a hyperlink.
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.
deleted this as it was a duplicate.
already present in a new ### Install kubectl for Windows (optional)
near the bottom.
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
By default, tokens expire after 24 hours. If you are joining a node to the cluster after the current token has expired. You can create a new token by running the following command on the control plane node: | ||
|
||
```bash | ||
kubeadm token create |
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.
kubeadm token create | |
# Run this on a control plane node | |
sudo kubeadm token create |
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, minus # Run this on a control plane node
. the prev sentence already mentions it.
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.
Should we move the steps about creating kubeadm join tokens to install-kubeadm.md
and reference that from both the windows and linux docs?
It looks like some of the docs are duplicated here
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
* `curl.exe` is installed and present in the `PATH` environment variable. | ||
* A running kubeadm cluster created by `kubeadm init` and following the steps | ||
in the document [Creating a cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/). | ||
|
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.
You'll also need a server running Windows, and administrative access to the server (just having the license is not enough to proceed).
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.
attempted to reword the steps.
@neolit123 once you've got the feedback you'd like, you might want to mark this as draft to indicate that you think it needs more work before it can merge. |
If you're an approver for English and you LGTM this and you need a second person to approve because this is a change to the live site: you can treat this message as grounds to approve it. The change as described above is well worth making. |
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Show resolved
Hide resolved
cd2cdbf
to
5eddc43
Compare
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
|
||
```PowerShell | ||
curl.exe -LO https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/hostprocess/Install-Containerd.ps1 | ||
.\Install-Containerd.ps1 -ContainerDVersion 1.7.1 |
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.
.\Install-Containerd.ps1 -ContainerDVersion 1.7.1 | |
.\Install-Containerd.ps1 -ContainerDVersion 1.7.22 |
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.
should we point to the containerd runtime docs here instead? https://kubernetes.io/docs/setup/production-environment/container-runtimes/#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.
i did not notice that there are windows install steps in https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd (inside the getting started link) that's great because we can just add a prereq for a container runtime and remove this step from here.
ideally we should break the follwing into linux/windows eventually too:
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl
and maybe have PrepareNode.ps be the install step for windows in that guide.
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.
the biggest differences between those docs and what we have are
- Checking and enabling the Hyper-V feature - which I don't think we care about for the purposes of this document
- Setting the CNI bin and CNI config dir's in the containerd config - I think we do want this
I think if we can get the containerd docs updated to create and set the cni bin/config dirs in the containerd setup script we can move away from the containerd setup doc in sig-windows-tools.
@jsturtevant - WDYT?
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.
agree, That info should live in the containerd install doc
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 though about unrolling the install-containerd script but think i'm going to leave this task to SIG Windows. my main problem here is that i have no way to test the containerd install and CNI setup, ATM.
also, it seems out of scope of the PR.
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
5eddc43
to
04a73fc
Compare
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md
Outdated
Show resolved
Hide resolved
I get the sense that this is ready for a pair (Linux, Windows) of tech LGTMs. |
Most of the Linux part is the same as before. Only some structure changes for Linux. Overall LGTM, but I don't have enough testing or knowledge about windows node. So leave to SIG-Windows to give the LGTM. |
Adjust the "create a kubeadm cluster" page to link to two separate task pages for adding Linux / Windows worker nodes. Base the Windows page on the existing document: https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/guides/guide-for-adding-windows-node.md
04a73fc
to
65107c7
Compare
@neolit123 you held this PR. When [ie, what conditions must be met] is it OK to unhold? |
just a precaution. |
@marosset @jsturtevant please review again. looking for LGTM on the Windows side. |
LGTM for Windows steps thanks @neolit123! |
/approve |
[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 |
/lgtm Tech reviews look done |
LGTM label has been added. Git tree hash: c79b9486f57d0b75e48d2161f5b033f0ab09754e
|
Description
Adjust the "create a kubeadm cluster" page to link to two separate task pages for adding Linux / Windows worker nodes.
Base the Windows page on the existing document:
https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/guides/guide-for-adding-windows-node.md
note: this is a PR for the main branch (not dev-1.32)
Issue
Closes #44248
xref