none: Allow host IP to be settable #2762

elioengcomp · 2018-04-23T16:40:28Z

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.26.1

OS (e.g. from /etc/os-release): Debian GNU/Linux 9 (stretch)
VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): none
ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
Install tools:
Others:

What happened: I'm getting a broken cluster everytime my host IP changes. It looks like the Pods keep trying to reach the host using the old IP. I tried to set the host IP by starting minikube with the following command, but it did not work:

minikube start --vm-driver=none --apiserver-name=localhost --apiserver-ips=127.0.0.1 --extra-config=kubelet.node-ip=127.0.0.1

What you expected to happen: I would like to be able to set the host IP to make my minikube installation survive network changes.

How to reproduce it (as minimally and precisely as possible):

Start a minikube cluster using vm-driver=none
Deploy an application to the cluster (It can be the dashboard)
Stop minikube
Change the host IP address
Restart minikube
Try to access the application.

Output of minikube logs (if applicable):

Anything else do we need to know:

The text was updated successfully, but these errors were encountered:

ntr-808 · 2018-04-24T06:20:44Z

i believe you are supposed to specify a bridge network.
from the readme:

NOTE: Minikube also supports a --vm-driver=none option that runs the Kubernetes components on the host and not in a VM. Docker is required to use this driver but no hypervisor. If you use --vm-driver=none, be sure to specify a bridge network for docker. Otherwise it might change between network restarts, causing loss of connectivity to your cluster.

elioengcomp · 2018-04-24T16:13:14Z

@Margh can you provide more details about this?

My daemon.json looks like this:

{
    "bip": "172.17.1.0/16"
}

ToddMorrill · 2018-05-31T22:51:33Z

Second the above question. I'm struggling to find clear instructions on how to create a bridge network. The closest thing I can find is this, which doesn't really explain anything or solve the problem.

I'm not positive on why do we ever need to pick a machine's external IP for this. Alongside other things, this prohibits using `minikube --vm-driver=none` on machines without Internet connectivity, which is stupid. Fixes kubernetes#3013, kubernetes#2762 and possibly many more similar issues.

fejta-bot · 2018-08-29T23:45:51Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

intelfx · 2018-08-30T00:47:32Z

/remove-lifecycle stale

spstarr · 2018-09-20T02:11:51Z

--vm-driver=none isn't just for hosts it can be for VMs already created, which is what I use it for.

Except I'd like to be able to choose what interface or IP to bind the cluster.

Right now, I sort of cheat, I use the Docker IP network and route to it from outside the VM, but trying to use Ingress with minikube doesn't work since it won't let me set the IP i want the cluster to be available on (to connect to the pods within the cluster) and Flannel with minikube doesn't work (the example yaml fails for some reason).

fejta-bot · 2018-12-19T02:54:47Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

I'm not positive on why do we ever need to pick a machine's external IP for this. Alongside other things, this prohibits using `minikube --vm-driver=none` on machines without Internet connectivity, which is stupid. Fixes kubernetes#3013, kubernetes#2762 and possibly many more similar issues.

fejta-bot · 2019-01-18T03:40:13Z

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

tstromberg · 2019-01-24T16:42:36Z

Fixed by intelfx@7535abe

tstromberg · 2019-05-22T00:08:59Z

Looks like I may have been mistaken about this being fixed.

rodjjo · 2019-06-18T17:53:51Z

minikube start --vm-driver=none --apiserver-name=localhost --apiserver-ips=127.0.0.1 --extra-conf=kubelet.node-ip=127.0.0.1

did you mean --extra-config not --extra-conf ?

elioengcomp · 2019-06-18T19:01:24Z

I think so. Just fixed it.

rodjjo · 2019-06-18T19:29:31Z

@elioengcomp

Mabye you can reuse minikube after ip changes by running:

export CHANGE_MINIKUBE_NONE_USER=true &&  minikube update-context && sudo systemctl restart kubelet && sudo minikube start --vm-driver=none --memory=8192 --kubernetes-version=v1.14.3

^ that does not solve the problem but at least you can still using minikube without reinstalling it.

I updated this comment replacing the command by the one i have tested on my machine.

maybe you have to run minikube stop before running it

elioengcomp · 2019-06-18T20:35:55Z

Thanks for the tip @rodjjo. It has been a while since I was working on this. I will give it a try when I have the chance.

fejta-bot · 2019-09-16T22:49:05Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

tstromberg · 2019-09-20T18:09:03Z

Closing as there is apparently a workaround.

raul1991 · 2019-10-16T16:11:49Z

Closing as there is apparently a workaround.

and what is that ? Can you copy that again here ?

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 29, 2018

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 30, 2018

tstromberg added kind/feature Categorizes issue or PR as related to a new feature. area/networking networking issues co/none-driver labels Sep 19, 2018

tstromberg mentioned this issue Sep 19, 2018

Do not require external IP address in minikube --vm-driver=none mode #3013

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 19, 2018

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 18, 2019

tstromberg closed this as completed Jan 24, 2019

tstromberg added the triage/obsolete Bugs that no longer occur in the latest stable release label Jan 24, 2019

tstromberg reopened this May 22, 2019

tstromberg changed the title ~~Set host IP for vm-driver=none~~ none: Allow host IP to be settable May 22, 2019

tstromberg mentioned this issue May 22, 2019

none: bind to the localhost interface by default #4313

Open

tstromberg added the r/2019q2 Issue was last reviewed 2019q2 label May 22, 2019

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 16, 2019

tstromberg closed this as completed Sep 20, 2019

woodcockjosh mentioned this issue Sep 30, 2019

proposal: Enable host OS dns resolution of cluster ingress host names #5494

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

none: Allow host IP to be settable #2762

none: Allow host IP to be settable #2762

elioengcomp commented Apr 23, 2018 •

edited

Loading

ntr-808 commented Apr 24, 2018

elioengcomp commented Apr 24, 2018

ToddMorrill commented May 31, 2018

fejta-bot commented Aug 29, 2018

intelfx commented Aug 30, 2018

spstarr commented Sep 20, 2018 •

edited

Loading

fejta-bot commented Dec 19, 2018

fejta-bot commented Jan 18, 2019

tstromberg commented Jan 24, 2019

tstromberg commented May 22, 2019

rodjjo commented Jun 18, 2019 •

edited

Loading

elioengcomp commented Jun 18, 2019

rodjjo commented Jun 18, 2019 •

edited

Loading

elioengcomp commented Jun 18, 2019

fejta-bot commented Sep 16, 2019

tstromberg commented Sep 20, 2019

raul1991 commented Oct 16, 2019

none: Allow host IP to be settable #2762

none: Allow host IP to be settable #2762

Comments

elioengcomp commented Apr 23, 2018 • edited Loading

ntr-808 commented Apr 24, 2018

elioengcomp commented Apr 24, 2018

ToddMorrill commented May 31, 2018

fejta-bot commented Aug 29, 2018

intelfx commented Aug 30, 2018

spstarr commented Sep 20, 2018 • edited Loading

fejta-bot commented Dec 19, 2018

fejta-bot commented Jan 18, 2019

tstromberg commented Jan 24, 2019

tstromberg commented May 22, 2019

rodjjo commented Jun 18, 2019 • edited Loading

elioengcomp commented Jun 18, 2019

rodjjo commented Jun 18, 2019 • edited Loading

elioengcomp commented Jun 18, 2019

fejta-bot commented Sep 16, 2019

tstromberg commented Sep 20, 2019

raul1991 commented Oct 16, 2019

elioengcomp commented Apr 23, 2018 •

edited

Loading

spstarr commented Sep 20, 2018 •

edited

Loading

rodjjo commented Jun 18, 2019 •

edited

Loading

rodjjo commented Jun 18, 2019 •

edited

Loading