You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For minikube v1.16+, Pixie is missing service info for traced HTTP requests. This can be immediately seen in the Service Graph in the px/cluster Live View - the graph does not show any traffic.
Startup a minikube cluster: minikube start --driver=hyperkit --cpus=4 --memory=8000 -p=minikube-test-cluster
px demo deploy px-sock-shop
As a workaround, you can enable the --cni=flannel flag when starting up minikube:
just an FYI: --cni=calico also works. So it seems really any "explicit" CNI works, but the default CNI of using a simple docker bridge-network does not work.
One of the effects not mentioned in the issue above is that when viewing (for example) HTTP events, all source IPs are mapped to the IP of the docker0 interface in minikube which is 172.17.0.1 by default.