Add proposal for kubeadm-local-cluster tool #629
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
|
@kubernetes/sig-testing-feature-requests assuming you guys are responsible for hack/local-up-cluster - this should be of interest to you |
|
@Kargakis: These labels do not exist in this repository: 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. I understand the commands that are listed here. |
|
@timothysc: These labels do not exist in this repository: 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. I understand the commands that are listed here. |
|
local-up-cluster.sh supports all runtimes (including CRI runtimes) today, how kubeadm-local-cluster could support other runtimes besides docker, since dind is only for docker? |
|
@feiskyer I don't think local-up-cluster is going away, this should just replace the docker parts of it. |
|
@feiskyer re CRI implementations, actually we use DIND just fine for Virtlet work, also Virtlet's demo script is based on DIND, too. We can do this thanks to the CRI proxy mechanism which makes it possible to run CRI implementations as DaemonSets and deploy them via single @Kargakis yes, I think the DIND mechanism cannot completely replace local-up-cluster. Yet I think that after Go rewrite it'll be possible to make multiple backends for this local cluster tool, including one that works in a way similar to local-up-cluster. This is currently out of scope of this proposal though. |
k8s-github-robot
added
the
size/L
|
This PR hasn't been active in 112 days. Closing this PR. Please reopen if you would like to work towards merging this change, if/when the PR is ready for the next round of review. cc @calebamiles @idvoretskyi @ivan4th You can add 'keep-open' label to prevent this from happening again, or add a comment to keep it open another 90 days |
* sort steering by last name cc @craigbox * Sort April based on Kyle Nassi
Moving the proposal from kubernetes/kubeadm#236 per sig-cluster-lifecycle suggestion.
A version of the local cluster tool described here exists in the form of kubeadm-dind-cluster project (Go version is not here yet). The differences are described closer to the end of the document.
It's yet to be decided where the tool should live (keep the old location in Mirantis github repo, move to kubernetes-incubator or some other option).
I'll be showing a demo of existing DIND solution (
kubeadm-dind-cluster) today on ContribX meeting (17 May 2017).