Improve topology view pod --> service --> pod traffic

[eranra]

Today the view in the topology looks like::

A ---------> B
!
!----------> S

So that customers are not aware that there is no direct traffic from A --> B and instead the traffic is actually thru S. We need to make it clear that A -->B is not direct traffic. This can be done by using netobserv/flowlogs-pipeline#214 configuration into L2 and changing the edges in the visualization (for example lighter gray, or dotted ... ).

Note: This might be a temporal solution until we will be able to identify the traffic as starting in the S node and not in A.

[github-actions]

Congratulations for contributing your first netobserv-operator issue

[eranra]

^^^ @amorenoz FYI

[eranra]

@jpinsonneau I believe that we had good conversation on that area but we are a bit stuck :-( maybe we need a session dedicated to this issue ... show how this looks in the UI and discuss what we should do??

[jpinsonneau]

Do we need netobserv/flowlogs-pipeline#214 first ?

Else yes we can find a time slot to discuss about this subject 👍

[eranra]

@jpinsonneau I am not sure that netobserv/flowlogs-pipeline#214 will solve this. I thought it might help but we never ended the test. the last statement from @amorenoz was that it might be that what I saw in my environment was due to some other things and not based on changes to the MAC address by OVS/N but maybe even if this is correct it does make sense to think on this area over a meeting.