Unexpected edges being rendered

[2opremio]

Maybe a duplicate of https://github.com/weaveworks/scope/issues/520 but I have a consistent way to reproduce it:

# create kubernetes cluster
(cd service && infra/local-k8s up )

git clone git@github.com:2opremio/craft-kubernetes-workshop.git 
cd craft-kubernetes-workshop/kubernetes
kubectl create secret generic tls-certs --from-file=tls
kubectl create configmap nginx-frontend-conf --from-file=nginx/frontend.conf
kubectl create -f deployments/hello.yaml
kubectl create -f services/hello.yaml
kubectl create -f deployments/auth.yaml
kubectl create -f services/auth.yaml 
kubectl create -f deployments/frontend.yaml
kubectl create -f services/frontend.yaml 

curl https://github.com/tsenart/vegeta/releases/download/v6.1.0/vegeta-v6.1.0-linux-amd64.tar.gz
tar -xvzf vegeta-v6.1.0-linux-amd64.tar.gz
echo "GET https://$(kubectl get service  frontend  --template '{{.spec.clusterIP}}')" | ./vegeta attack -connections 1  -insecure -duration 0 -rate 20  > /dev/null

You will get edges from the nginx container to kubernetes components to between which there is no communication. For instance:

nginx is not talking to apiserver, scheduler nor controllermanager. Sometimes it also gets edges to etcd.

Report: report_madeup_edges.json.gz

[tomwilkie]

I think we should close this as a dupe of #520; we have plenty of ways of reproducing it. @2opremio thoughts?