-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Run localkube outside of a container in the guest VM. #8
Comments
Currently, every release of localkube ships with a binary that can be run on Linux - will need to be tested more extensively, though. https://github.com/redspread/localkube/releases/tag/v1.2.1-v1 |
Yeah I gave it a try and it runs, but it seems to expect some stuff from the Weave base image it's usually run inside. This should be pretty straightforward, just need to find all the dependencies and make sure they're present. |
Okay cool, the only dependency is Weave, and that the proper cgroups are set up. This script shows you how to bring up localkube once Weave is installed. |
Why a weave dep? If we want But it would be really cool to support either flannel or weave OOTB for the minikube server. That way we could reuse the minikube server for docker-multinode. WDYT @vishh? @mfburnett When we add things to core, we should make sure |
Yeah, ideally, the network overlay would run from within localkube, but we couldn't find an overlay that made this easy and allowed users to bring their own Docker daemon. We're not attached to Weave - open to suggestions on that front. And yup, working on making |
Why do we even need networking support for "local cluster"? Doesn't the On Tue, Apr 19, 2016 at 2:00 PM, Mackenzie Burnett <[email protected]
|
Hm, as far as I know we need a network overlay to make the pod-per-IP requirement work outside of GCE |
For a single node scenario, we don't need a network plugin. On Tue, Apr 19, 2016 at 2:13 PM, Mackenzie Burnett <[email protected]
|
Is there no plan to provide an ability to extend the cluster with extra VMs, to simulate any realistic use-cases? |
@errordeveloper Not in the near future. |
Resolved with #44 |
Enable CNI
# This is the 1st commit message: Fix doc comment version.gitCommitID doc # This is the commit message kubernetes#2: Add hyperkit doc # This is the commit message kubernetes#3: Add commit id to docker-machine-driver-kvm2 version # This is the commit message kubernetes#4: removed label selector for registry-proxy daemonset # This is the commit message kubernetes#5: Add support to custom qemu uri on kvm2 driver # This is the commit message kubernetes#6: Improve hyperkit vm stop # This is the commit message kubernetes#7: Make virtualbox DNS settings configurable # This is the commit message kubernetes#8: added integration tests for registry addon
No description provided.
The text was updated successfully, but these errors were encountered: