I configured my Ubuntu server (192.168.1.6) with minikube and kvm2, all seems ok
$ minikube start --vm-driver=kvm2 Starting local
Kubernetes v1.8.0 cluster... Starting VM... Getting VM IP address...
Moving files into cluster... Setting up certs... Connecting to
cluster... Setting up kubeconfig... Starting cluster components...
Kubectl is now configured to use the cluster. Loading cached images
from config file.
$ kubectl get po --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default node-hello-6dd6c8bb-j672z 1/1 Running 3 1d
kube-system kube-addon-manager-minikube 1/1 Running 4 3d
kube-system kube-dns-86f6f55dd5-27ttl 3/3 Running 12 3d
kube-system kubernetes-dashboard-77c67f7cd9-wxsg9 1/1 Running 4 3d
kube-system kubernetes-dashboard-n2fd4 1/1 Running 4 3d
kube-system storage-provisioner
$ minikube dashboard --url
http://192.168.39.172:30000
But I cant't access on this IP from my home network on my computer (192.168.1.10).
When I put telnet 192.168.39.172 30000 I got error IP not reachable.
EDIT :
I think I need to use SSH port forwarding
kubectl proxy &
ssh -R 30000:127.0.0.1:8001 docker@192.168.39.172
but I can't open the port 30000 because it already listen in the Ubuntu server
tcp 0 0 :::30000 :::* LISTEN
How can I do that ?
Thanks
I was facing same issue, then I did curl on the dashboard url:
curl <>:30000/
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 990 100 990 0 0 966k 0 --:--:-- --:--:-- --:--:-- 966k **You are using an outdated</strong> browser. Please upgrade your browser</a> to improve your experience.</p>**
I tried to open the same url from google chrome and was able to see the dashboard.
Sorry if the answer is not helpful, shared what I experienced.
But I cant't access on this IP from my home network.If I understand correctly, that you try to access minikube started on one computer from another one in your local network, then it will not work. At least not until the client knows how to route traffic so that it can reach 192.168.39.172 which is a local bridge interface for your minikube VM.
One of the solutions could be to set up additional routing rule to point 192.168.39.0/24 to the IP of your minikube host.
Another would be to run kubectl proxy --address 0.0.0.0 on minikube host so that api is exposed on all interfaces (please mind that kubectl proxy adds authorization on it's own, meaning that if you open it like this, anything can access the API as you, without any auth)