Component operator is often OOMKill

[LHozzan]

• situation occurring across our fleet
• I dont see any anomalies from metrics, except memory usage
  
• in previous run (marked yellow) component using more RAM
• after OOMKill event (marked orange) RAM usage dropped
• it seems, that in the memory space of the component are holding unrequired data, which can cause after some time of usage OOMKill event (I guess! I am not sure)
• it is strange, that the component using same settings, managing same operators, but after OOMKill event is satisfied with lower memory usage
  

I would like to kindly ask to continue with the investigation in source code. Goal is, that operator will consume only constant and predictable amount of memory. If the state isnt possible to reach, I would like to ask you for explanation, why it isnt.

If you need more information, please, dont hesitate to ask and I will provide them.

[github-actions]

This issue has been marked as stale because it has not had activity for 180 days. It will be closed in 7 days if no further activity occurs.

[LHozzan]

Problem was meantime fixed by adding more resources.

• requests: 750MB
• limits: 1500MB