• Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • eBPF, Operator
    • None
    • packet-capture-ebpf
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • L

      For troubleshooting, provide a mechanism to trigger packet capture on demand (full packet content), targeting a specific pod or a set of pods (e.g. by controller name or by labels).

      A new CRD must be created to describe the packet-capture setup. It should include:

      • The target pod(s) identification (pod name, or controller name, or pod labels)
      • Some optional filters:
        • Flow direction: ingress / egress / both
        • Peer name / type / ip / port
      • Time limit and/or packet count limit (capture first N packets)
      • Sampling

      A kubectl / oc plugin should also be created to capture from the command line and get the output

      Note, there can be a follow-up to add an UI

              Unassigned Unassigned
              jtakvori Joel Takvorian
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: