-
Notifications
You must be signed in to change notification settings - Fork 123
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
Adding containerd support to kubeadm related scripts/specs/etc #112
Adding containerd support to kubeadm related scripts/specs/etc #112
Conversation
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marosset, michmike 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 |
5bb3f34
to
2774a0b
Compare
/assign @benmoss @jsturtevant I think this is ready for review. |
I've started some doc updates for using these changes kubernetes/website#24862 Related to kubernetes/enhancements#1001 |
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.
Left a few comments.
9e29744
to
dac37db
Compare
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 left a few notes/open questions on the CNI configs
Over all looks good. Had one question on the PA address section |
detect docker/containerd via named pipes PR feedback from David PR feedback
dac8d9c
to
64367ef
Compare
I was able to join a node:
|
/lgtm |
Adding support for configuring a cluster that uses containerd to the existing kubeadm implementionstations.
Verify the following:
Notes:
Install-containerd.ps1 needs to be downloaded and run before running PrepareNode.ps1.
This assumes a completely vanilla Windows installation and may need to enable Windows features which will require a reboot.
After running Install-Containerd.ps1 to completion run PrepaseNode.ps1 -ContainerRuntime containerd.
Kube-proxy/CNI deployment should be the same as with docker.
All of these will be captured in updates to kubernetes/website updates to https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/