Skip to content
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

Closed
dlorenc opened this issue Apr 19, 2016 · 11 comments
Closed

Run localkube outside of a container in the guest VM. #8

dlorenc opened this issue Apr 19, 2016 · 11 comments
Milestone

Comments

@dlorenc
Copy link
Contributor

dlorenc commented Apr 19, 2016

No description provided.

@mfburnett
Copy link

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

@dlorenc
Copy link
Contributor Author

dlorenc commented Apr 19, 2016

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.

@mfburnett
Copy link

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.

@luxas
Copy link
Member

luxas commented Apr 19, 2016

Why a weave dep? If we want minikube not to use networking (local machine only), it seems a bit strange.

But it would be really cool to support either flannel or weave OOTB for the minikube server.
We just don't have to use it for the minikube client.

That way we could reuse the minikube server for docker-multinode. WDYT @vishh?

@mfburnett When we add things to core, we should make sure serviceAccounts work, as it's a really important part of Kubernetes.

@mfburnett
Copy link

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 serviceAccounts work!

@vishh
Copy link
Contributor

vishh commented Apr 19, 2016

Why do we even need networking support for "local cluster"? Doesn't the
default bridge network work?

On Tue, Apr 19, 2016 at 2:00 PM, Mackenzie Burnett <[email protected]

wrote:

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 serviceAccounts work!


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#8 (comment)

@mfburnett
Copy link

mfburnett commented Apr 19, 2016

Hm, as far as I know we need a network overlay to make the pod-per-IP requirement work outside of GCE

@vishh
Copy link
Contributor

vishh commented Apr 19, 2016

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]

wrote:

Hm, as far as I know
https://github.com/kubernetes/kubernetes/blob/master/docs/design/networking.md#implementation
we need an additional overlay to make the pod-per-IP requirement work
outside of GCE


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#8 (comment)

@errordeveloper
Copy link
Member

Is there no plan to provide an ability to extend the cluster with extra VMs, to simulate any realistic use-cases?

@vishh
Copy link
Contributor

vishh commented Apr 29, 2016

@errordeveloper Not in the near future. minikube is primarily meant to test kube apps on localhost before running them in real clusters.

@dlorenc
Copy link
Contributor Author

dlorenc commented May 6, 2016

Resolved with #44

@dlorenc dlorenc closed this as completed May 6, 2016
jimmidyson added a commit to jimmidyson/minikube that referenced this issue Jul 14, 2016
s-urbaniak pushed a commit to s-urbaniak/minikube that referenced this issue Oct 13, 2016
castlemilk pushed a commit to castlemilk/minikube that referenced this issue Jun 29, 2019
# 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants