Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-38367

iptables-alerter causes DaemonSetMisScheduled alerts in clusters with infra nodes

XMLWordPrintable

    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      DaemonSet "iptables-alerter" is suppose to run on all nodes, based on discussion [1]. However, the DaemonSet is not configure to tolerant any taints. If I set up a special MachineSet with taint, those nodes will not get the "iptables-alerter" pods running.
      
      [1]: https://redhat-internal.slack.com/archives/CFFSAHWHF/p1723230550938349?thread_ts=1723213664.230299&cid=CFFSAHWHF
      
          

      Version-Release number of selected component (if applicable):

      4.16
          

      How reproducible:

      Create a machineset with taint
          

      Steps to Reproduce:

          1. Create a new MachineSet with taint set 
            taints:
              - effect: NoSchedule
                key: node-role.kubernetes.io/infra
                value: reserved
          2. Observe the Pods on the Node
      
          

      Actual results:

      "iptables-alerter" is not scheduled to the Node.
          

      Expected results:

      "iptables-alerter" is running on the Node.
          

      Additional info:

      
          

              dwinship@redhat.com Dan Winship
              bechen@redhat.com Bear Chen
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: