-
Notifications
You must be signed in to change notification settings - Fork 6.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
Adopt kubeadm tool for cluster creation #553
Comments
@bogdando + @Smana yeah, this sounds good. let me do a couple of things before i merge in and find intersecting points with kubespray (if this is ok)? i am in the process of adding a couple of things; the obvious is centos. i contacted maintainers of a kubeadm/centos/ansible project, and they were fine with merging the efforts. we should probably talk about how you want to handle sdn's too. i was planning on adding sdn's today for:
|
@v1k0d3n sure, please also join to my WIP patch review |
Related issue that makes integration with CM very painful kubernetes/kubernetes#35133 |
Another blocker issue kubernetes/kubernetes#33729 |
And multi master steps are unclear kubernetes/kubernetes#35188 |
There is also yet possible to use hyperkube for kubeadm kubernetes/kubernetes#35190 |
This is yet doable, closing. But I continue my WIP branch tho |
We should keep this open and let it be a roadmap item. |
For subscribers to this thread, the work on the kubespray side has now begun 🎉 |
this is great news @luxas! |
Should we open more targeted issues for implementing HA/upgrades/setting up e2es etc using kubeadm or ...? |
@luxas of course. I will open them |
Great please cc me |
I can't believe my eyes this one is done now! Well done folks, really, thank you for taking care of this! |
We should delegate some CM tasks to the kubeadm tool in Kubernetes.
For the start, that may be a certificates management for k8s cluster nodes. Because this is the most time consuming operation on a large scale.
Perhaps we could do that by adopting https://github.com/att-comdev/halcyon-kubernetes work to Kargo
The text was updated successfully, but these errors were encountered: