Version of Eraser
No response
Expected Behavior
Hello Eraser team,
We recently witnessed a case where the eraser-controller-manager pod out of memory caused cluster OOM, the behavior we observed werre:
eraser-controller-manager OOM -> each restart creates a imagejob -> each imagejob creates pods per node -> more pressure on apiserver
Can you help investigate on this issue?
Actual Behavior
No response
Steps To Reproduce
No response
Are you willing to submit PRs to contribute to this bug fix?