area/networkinghelp wantedkind/featurelifecycle/frozenpriority/awaiting-more-evidence
Description
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Perhaps Both
Please provide the following details:
Environment:
Windows 10 or Mac High Sierra
Minikube version (use minikube version): ALL
- Install tools: choco or homebrew
What happened: Minikube ip changes after stopping and starting it. This is inconsistent as sometimes it doesn't change What you expected to happen: Minikube ip to be configurable How to reproduce it (as minimally and precisely as possible): minikube start minikube ip minikube delete minikube start minikube ip
As a feature request, I would appreciate it if there was a flag that could specify that IP when you run minikube start.