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

Pods with > 1 container making connections do not show any connections #1494

Closed
paulbellamy opened this issue May 12, 2016 · 2 comments
Closed
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it k8s Pertains to integration with Kubernetes
Milestone

Comments

@paulbellamy
Copy link
Contributor

I believe this is because they share a network namespace, so the endpoint cannot be attributed to a container, and we drop it.

Report attached report.zip

@paulbellamy paulbellamy added the bug Broken end user or developer functionality; not working as the developers intended it label May 12, 2016
@tomwilkie
Copy link
Contributor

So given a pod has a unique IP, we could do another conntracked edge join on the pod topology to fix this.

I was previously against doing this, but with the recent improvements to conntrack, it might be worth it.

@tomwilkie tomwilkie added the k8s Pertains to integration with Kubernetes label May 12, 2016
@tomwilkie tomwilkie added this to the Post-1.0 milestone May 16, 2016
@tomwilkie
Copy link
Contributor

We're hitting this visualising Weave Cloud, and just had reports from a third party that they are also hitting this and they want to use scope in their Dockercon demo. So I'd like to try and get a fix in for 0.16 tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it k8s Pertains to integration with Kubernetes
Projects
None yet
Development

No branches or pull requests

2 participants