Closed binchenX closed 2 years ago
A few other Minikube related issues: https://github.com/istio/istio.io/issues/9340 and https://github.com/istio/istio.io/issues/8286.
Running through the scenario: Using the Docker hypervisor driver (VMware and hyper kit have issues (This VM is having trouble accessing https://k8s.gcr.io and istio fails to install as it can't pull the images)
When using mk tunnel
:
service/istio-ingressgateway LoadBalancer 10.100.218.72 127.0.0.1
15021:31939/TCP,80:30771/TCP,443:30942/TCP,31400:32513/TCP,15443:30881/TCP 9m5s
When not:
service/istio-ingressgateway LoadBalancer 10.100.218.72 <pending>
15021:31939/TCP,80:30771/TCP,443:30942/TCP,31400:32513/TCP,15443:30881/TCP 12m
If using the tunnel: http://127.0.0.1:80/productpage works. The values are determined using the flow where an external IP is defined which it is.
The old non mk tunnel ip/port does not seem to work.
I am able to run things with a virtual box VM similarly. It does have a warning about using a more preferred driver.
Following instructions regarding how to get the host and IP for the ingress 1 does not work for in minikube environment (see below) for me.
It will give you ingress host and port with something like
192.168.59.100:31873
and curl it willHowever, if I follow the steps listed in the official minikbue doc,
Notably, for IP using the
EXTERNAL-IP column
, instead of using 'minikube IP'Noticed that this is the exact same instruction for
other platforms
as listed in 1.And that instruction will give me the result I expect:
Not sure if there is something peculiar about my setup or this is a mistake on the doc but seems minikube can use same instructions as "other platforms", at least in my environment..
Minikube environment
tldr: Minikube on Mac, with dockker as the driver