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

netobserv-plugin pod keep recreating in schedule disabled node

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 277
    • None
    • None
    • Hide
      Previously, there was a default toleration set up on all Network Observability component to allow them being scheduled on any node, including those tainted with NoSchedule. This could potentially block cluster upgrades. This default toleration is now only kept for the eBPF Agents and Flowlogs-Pipeline (the latter just when in Direct mode), and not for the Console plugin and Flowlogs-Pipeline (when in Kafka mode).
      Moreover, despite the Tolerations being configurable in FlowCollector, it was previously not possible to replace the Tolerations with an empty list. It is now possible to do so.
      Show
      Previously, there was a default toleration set up on all Network Observability component to allow them being scheduled on any node, including those tainted with NoSchedule. This could potentially block cluster upgrades. This default toleration is now only kept for the eBPF Agents and Flowlogs-Pipeline (the latter just when in Direct mode), and not for the Console plugin and Flowlogs-Pipeline (when in Kafka mode). Moreover, despite the Tolerations being configurable in FlowCollector, it was previously not possible to replace the Tolerations with an empty list. It is now possible to do so.

      Description of problem:

      netobserv-plugin pod keep being recreated in a node that schedule is disabled

      Steps to Reproduce:

      1.deploy netobserv operator with console plugin
2.disable node schedule
3.delete console plugin pod

      Actual results:

      console plugin pod recreated in the node with schedule disabled

      Expected results:

      console plugin pod create in other nodes with schedule enabled

       

      Workaround:

      Tolerations can be overriden by configuration in FlowCollector, however a second bug makes it impossible to replace the default toleration with an empty list of tolerations. The workaround is thus to create a dummy toleration for console plugin. To do so, edit FlowCollector with:

        consolePlugin:
    advanced:
      scheduling:
        tolerations:
          - key: dummy-key-to-satisfy-non-empty-list
            operator: Exists

              jtakvori Joel Takvorian
              rh-ee-dwan Di Wang
              None
              None
              None
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: