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

Namespace change in CRD result in duplicated ebpf agents

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • netobserv-1.2
    • netobserv-ocp4.12
    • eBPF
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 230
    • None
    • None
    • Hide
      Previously, after changing the `namespace` value from a FlowCollector spec, eBPF Agent pods running in the previous namespace would not get deleted as appropriate.
      With this patch, the pods running in the previous namespace are deleted as appropriate.
      Show
      Previously, after changing the `namespace` value from a FlowCollector spec, eBPF Agent pods running in the previous namespace would not get deleted as appropriate. With this patch, the pods running in the previous namespace are deleted as appropriate.

      Steps to reproduce:

      Create flowCollector with default values

      > netobserv-ebpf-agent pods are created in netobserv-privileged

      Update CRD namespace to netobserv2

      > new netobserv-ebpf-agent pods are created in netobserv2-privileged namespace

      > old pods are not deleted

      We should delete old pods to avoid duplicated (or keep previous namespace ?) 

        1. image (8).png
          170 kB
          Julien Pinsonneau

              jtakvori Joel Takvorian
              jpinsonn@redhat.com Julien Pinsonneau
              None
              None
              None
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: