Open c-kruse opened 8 months ago
This is probably a workaround for this?
This is probably a workaround for this?
* [Fixes phantom process records observed in the console UI skupper#1341](https://github.com/skupperproject/skupper/pull/1341)
They are related @jiridanek - but I'd hesitate to call either a workaround. The flow collector should be idempotent (fix in skupper/pull/1341), and from what I understand vanflow messages should be delivered only once to each consumer with some reliability regardless of van topology (the topic brought up in this issue.)
Hi, I'm interested in investigating this ticket. If there's any concern / issue with me investigating this ticket, please do not hesitate to let me know. Thanks, Karen
As discussed in the Skupper Team g chat, I am observing repeated delivery of vanflow messages. This was uncovered by an unrelated skupper collector bug. Thanks for following along @ted-ross! I suspect this issue is in the router, but I didn't know where to start trying to reproduce it without the control plane.
To reproduce:
skupper link create --namespace b token-a.yaml skupper token create --namespace b token-b.yaml
skupper link create --namespace c token-a.yaml skupper link create --namespace c token-b.yaml
apiVersion: apps/v1 kind: Deployment metadata: name: vanflow-logging labels: app: vanflow-logging spec: replicas: 1 selector: matchLabels: app: vanflow-logging template: metadata: labels: app: vanflow-logging spec: containers: