-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating
Learn OpenShift
By :
Starting from 4.16, OpenShift includes a DaemonSet called iptables-alerter that tries to detect if customers are using iptables in any of their pods. If yes, it logs Events warning them that iptables is going away in RHEL 10 in 2025. Like CoreDNS pods, iptables-alerter pods also fail to start on nodes with custom taints, however adding tolerations to this DaemonSet is not supported. This does not affect operations, only logging. Read more at [6].You can check if you are affected with oc get po -o wide -n openshift-network-operator:

As you can see, there are no such pods running on our infra nodes. This is a known issue that is being tracked in [7]. At the time of writing this chapter, there is no supported fix for this. An unsupported solution would be to change the Network CR to Unmanaged, so that it doesn't reset DaemonSet configuration, and add a toleration directly...
Change the font size
Change margin width
Change background colour