When a custom taint is set on a node the iptable-alerter will not start on that node. This taint can be an infra node for instance. The network operator does not allow for toleration modification.

    OCP 4.18

    100%

    1.Taint a note
    2.New pod is not triggered on the tainted node
    

    iptables-alerter is not started inthe tainted node

    Ideally the tolerations are se in more open way:

        tolerations:
        - operator: Exists

    Which ignores all taints. It would also be great if it would be possible to set customer tolerations in the operator.openshift.io/Network

The reason behind is that if an end user creates a new node and they set taints there. They cannot track all the openshift system components and set the right tolerations there as there is out fo their knowledge. Openshift should deal with this automatically.