Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1779

Port configured but not protocol results in no error in eBPF flow filtering

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • netobserv-1.7
    • netobserv-1.6, netobserv-1.6.1
    • eBPF
    • False
    • None
    • False
    • Hide
      Previously, eBPF flow filter on port(s) without specifying a protocol were ignored.
      Now, you can set eBPF flow filters independently on ports and / or protocols.
      Show
      Previously, eBPF flow filter on port(s) without specifying a protocol were ignored. Now, you can set eBPF flow filters independently on ports and / or protocols.
    • NetObserv - Sprint 258, NetObserv - Sprint 259
    • Moderate

      Configure eBPF flow filter as follows:

        agent:
    ebpf:
      flowFilter:
        enable: true
        action: Accept
        cidr: 0.0.0.0/0
        ports: 443

      Because 'protocol' is missing and is required, it does no eBPF filtering.  The user is left confused as to why filtering isn't happening.  Instead, it should report this error instead of accepting the configuration.

              jpinsonn@redhat.com Julien Pinsonneau
              stlee@redhat.com Steven Lee
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: