search

netobserv / multi-cloud-research

Research the area of multi-cloud network observability
Apache License 2.0
1 stars 3 forks source link

added config to map east/west subnet to a label #17

Closed KalmanMeth closed 1 year ago

eranra commented 1 year ago

image

eranra commented 1 year ago

@KalmanMeth, in the picture above, you can see the missing link we need to close with this PR. The view is currently showing only pods and the need is for the skupper-router from the east to talk with the skupper-router on the west

http://172.18.100.5:9001/?timeRange=300&limit=50&match=all&reporter=destination&function=last&type=bytes&recordType=flowLog&filters=dst_kind%3DPod%3Bsrc_kind%3DPod%3Bsrc_namespace%3Deast%2Cwest

eranra commented 1 year ago

image

eranra commented 1 year ago

The above view is focused just on the resources with the name skupper-serv-*" --- you see on the east side that theskupper service controllerpod is talking with172.18.101.12--- and other is noresolution` to that name ( on the east side ) but we know that this is the load-balancer service on the west side

eranra commented 1 year ago

image

eranra commented 1 year ago

So, if we knew to enrich the skupper-router IP ( 172.18.101.2) in this example that belongs to the west side when we work on the east side we should have seen the two sites connecting.

I hope that this makes sense + we will see very similar behavior with mbg and we need to support both

eranra commented 1 year ago

@KalmanMeth I tried to run the PR and got::

time=2023-05-28T14:19:51Z level=panic msg=unknown type add_label_if for transform.Network rule: {DstSubnet SubnetName add_label_if 172.18.100.2 subnet_east} component=transform.Network panic: (*logrus.Entry) 0xc00014cfc0

Maybe need to change to add_if ?