NETOBSERV-2071 CLI use cases for 1.8 #6
Conversation
|
maybe adding a usecase with filter on drop flows as that was one of the use cases we heard during f2f ? |
|
also another use case if watching N/S flows only or E/W flows only |
| You can cycle to different views using left / right arrow keys and change the displayed enrichment colomns using page up / down ones. | ||
| Also, to adapt to your screen height, you can increase / decrease the number of displayed flows using up / down arrow keys. | ||
|
|
||
| In this capture, we see that the traffic is blocked by OVS since it reports the `OVS_DROP_LAST_ACTION` drop cause. This probably means that a Network Policy is involved. |
There was a problem hiding this comment.
This stuff no longer available with network events support, u will use network events feature and look for drops actions instead
There was a problem hiding this comment.
ok I can rerun this scenario and see how it goes. I'm supposed to get both drop info + event here ?
There was a problem hiding this comment.
no drop for netpol just event, ovs team has dropped the drop cause when they created the new events hook they said we can't have both
There was a problem hiding this comment.
That means this will not displayed in overview drop cause graph anymore !
We may need a new graph for events here
There was a problem hiding this comment.
we will get still pkt drops but not for ovn netpol
There was a problem hiding this comment.
I actually don't get anything in the drops info in that case
Whereas the events are correct:
It's really confusing in terms of UX
There was a problem hiding this comment.
|
🙈 The PR is closed and the preview is expired. |
Added this in f958c46 |
jpinsonneau
force-pushed
the
cli_use_cases
branch
from
c96471d to
eb233c9
Compare
jpinsonneau
requested review from
jotak,
msherif1234,
OlivierCazade,
Amoghrd,
skrthomas,
stleerh and
memodi
| Once some traffic is captured, the output will look like: | ||
| }) | ||
|
|
||
| Cycle to the **network events** view. In this capture, we see that the traffic is blocked by a network policy since it reports the `NetpolNamespace` event. |
There was a problem hiding this comment.
This PR should provide a better output for the network events
There was a problem hiding this comment.
Awesome ! Do you have a screen ?
Else I will spin up a cluster
Thanks for the very detailed review @skrthomas ! that's awesome ! |
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Sara Thomas <[email protected]>
Co-authored-by: Amogh Rameshappa Devapura <[email protected]>
jpinsonneau
force-pushed
the
cli_use_cases
branch
from
152644b to
3fe27ea
Compare
|
Rebased without changes to see if the preview works now |
Updated concrete scenarios with 1.8 commands