Description of problem: High CPU usage (hitting the limit) for iptables-alerter pods and this issue is seen for some of the pods.

Command Output:
NAME                                CPU(cores)   MEMORY(bytes)
iptables-alerter-4wk77              0m           125Mi
iptables-alerter-5rdg6              11m          148Mi
iptables-alerter-5wzpn              0m           118Mi
iptables-alerter-8vz7s              0m           115Mi
iptables-alerter-9qfqc              11m          120Mi
iptables-alerter-k8kb5              0m           128Mi
iptables-alerter-km8x4              0m           116Mi
iptables-alerter-qblr2              10m          130Miname: iptables-alerter
    resources:
      limits:
        cpu: 10m
      requests:
        cpu: 10m
        memory: 65Mi 

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

How reproducible: This issue is reproducible in customer environment. 

Steps to Reproduce:

1. On OCP version 4.16 onward, the CPU usage  iptables-alerter pods is high i.e. hitting limit.

Actual results: The CPU usage of pods is hitting the limit. 

Expected results: The CPU usage of node should not hit the limit.

Additional info: More discussion in below slack thread.

https://redhat-internal.slack.com/archives/CDCP2LA9L/p1729893663428849

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms: OCP 4.16

Is it an  -> customer issue 

1. internal CI failure
2. customer issue / SD -
3. internal RedHat testing failure

If it is an internal RedHat testing failure: No

• Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).

If it is a CI failure: No

• Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
• Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
• Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
• When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
• If it's a connectivity issue,
• What is the srcNode, srcIP and srcNamespace and srcPodName?
• What is the dstNode, dstIP and dstNamespace and dstPodName?
• What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)

If it is a customer / SD issue:

• Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
• Don’t presume that Engineering has access to Salesforce.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
• Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
  • If the issue is in a customer namespace then provide a namespace inspect.
  • If it is a connectivity issue:
    • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What is the dstNode, dstNamespace, dstPodName and dstPodIP?
    • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
    • Please provide the UTC timestamp networking outage window from must-gather
    • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
  • If it is not a connectivity issue:
    • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.

• When showing the results from commands, include the entire command in the output.  
• For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
• For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components