The iptables-alerter daemonset does not tolerate custom taints in RHOCP 4.

Solution Verified - Updated -

Issue

  • The iptables-alerter DaemonSet should be able to tolerate custom taints to ensure full monitoring coverage across all nodes.
  • The openshift-network-operator/iptables-alerter DaemonSet is failing to deploy pods on nodes that have custom taints (e.g., infra nodes).
  • Creating a monitoring gap, as nodes with custom taints are not being checked for the creation of deprecated iptables rules.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content