-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NETOBSERV-330 Provide a way to filter Kubernetes-related flows #176
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I found a bug while implementing this https://issues.redhat.com/browse/NETOBSERV-399 |
My thoughts: If 'infra' is involved (src or dst or both) it should be 'infra' BTW: This applies to services and pods Hope this helps |
I think anywhere that 'app' appears should be included as "apps" traffic. Otherwise, you will miss router -> app. |
Exactly, we're missing ingress traffic coming to the application, that's the main issue with this approach I think |
@stleerh @jotak @eranra I would suggest to add a configurable regex that match ingress namespace. Default value: With that we can force these to appear in the application view: |
Good idea :) |
@jpinsonneau: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
thanks @jpinsonneau |
/approved |
Added
Traffic Scope
query options:It uses regex
(kube-|openshift-).*
with matches / does not matches operators on bothSrcNamespace
andDstNamespace