Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP requests missing service info on minikube v1.16+ #298

Open
htroisi opened this issue Jul 29, 2021 · 1 comment
Open

HTTP requests missing service info on minikube v1.16+ #298

htroisi opened this issue Jul 29, 2021 · 1 comment
Assignees
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@htroisi
Copy link
Contributor

htroisi commented Jul 29, 2021

Bug Description
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.

Repro Steps

  1. Startup a minikube cluster: minikube start --driver=hyperkit --cpus=4 --memory=8000 -p=minikube-test-cluster
  2. px deploy
  3. px demo deploy px-sock-shop

Temporary Workaround
As a workaround, you can enable the --cni=flannel flag when starting up minikube:

minikube start --driver=<kvm2|hyperkit> --cni=flannel --cpus=4 --memory=8000 -p=<cluster-name>

Next Steps
Further investigation is required to see what it is about minikube 1.16 that causes the issue. Definitely appears related to the CNI, but may also have something to do with the k8s version.

@zasgar zasgar added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 7, 2022
@clemenskol
Copy link
Contributor

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.

More details on selecting a CNI for minikube can be found here: https://minikube.sigs.k8s.io/docs/handbook/network_policy/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

4 participants