pelorus-operator-controller-manager-* pod is going into CrashLoopBackOff / oomkilled

[mpryc]

Increasing memory and cpu resources does fade out the issue, but it's still existing over time. Pelorus get's deployed correctly, just manager is crashing with oomkilled. Maybe it's related to the log growing up in the manager pod.

pelorus-operator-controller-manager-* pod is going into CrashLoopBackOff, however pelorus is deployed correctly.

I suspect there may be a problem with proper resources to that pod ?

Originally posted by @mpryc in #715 (comment)

[KevinMGranger]

Potentially solved by operator-framework/operator-sdk#6026

[mpryc]

Resolved with #741

Screenshot from 48h of running pod (attached) shows the problem with restarting pod is gone: