Context: If a customer sets a NoSchedule taint on some of their worker nodes, there are a few DaemonSets from operators that will not be able to schedule pods on those nodes. However, this can be solved by adding tolerations to the operator. An example of this is covered in this KCS solution: https://access.redhat.com/solutions/6592171

Issue: A customer has recently found that this solution will not work on ROSA HCP (v4.16) with the network operator (v4.16.30) daemonset iptables-alerter. The operator is rolling back the manual changes made for tolerations and the iptables-alerter cannot be scheduled on the nodes with NoSchedule taints.