-
Bug
-
Resolution: Done
-
Minor
-
netobserv-1.8
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
NetObserv - Sprint 270, NetObserv - Sprint 271, NetObserv - Sprint 272, NetObserv - Sprint 273, NetObserv - Sprint 274, NetObserv - Sprint 275, NetObserv - Sprint 276
-
Proposed
-
Bug Fix
-
Description of problem:
NetObserv controller pod gets OOM killed for 500 nodes perf scenario
Steps to Reproduce:
1. Deploy Network Observability operator 2. Run 500 nodes perf scenario
Actual results:
Operator pod gets OOM killed
Expected results:
Operator pod should not get OOM killed
Upon doubling the memory in NetObserv CSV, the pod runs fine
Resources: Limits: Memory: 800Mi Requests: Cpu: 100m Memory: 200Mi