[Bug] Operator controller manager Pod OOMKilled and crash looping

[andrewazores]

Current Behavior

  containers:
    - resources:
        limits:
          cpu: '1'
          memory: 256Mi
        requests:
          cpu: 100m
          memory: 64Mi
....
lastState:
        terminated:
          exitCode: 137
          reason: OOMKilled
          startedAt: '2024-01-26T08:36:59Z'
          finishedAt: '2024-01-26T08:37:24Z'

operator-pod.log

Are the manager's resource limits hardcoded? Should this be increased by default and is there a way to make this configurable for the user?

cryostat-operator/config/manager/manager.yaml

Line 59 in 6ac7ec6

memory: 256Mi

Expected Behavior

No response

Steps To Reproduce

No response

Environment

No response

Anything else?

No response

[andrewazores]

https://sdk.operatorframework.io/docs/best-practices/managing-resources/#how-to-change-the-operatormanager-resources-values-when-under-olm-management

[andrewazores]

Users can/should do this via the OLM Subscription object as documented above if they need to adjust the values rather than rely on our defaults.

Question still remains whether we should adjust the defaults.

[ebaron]

I think the subscription is the only way to do it at the bundle level. It's probably worth increasing the limit. Judging from the log, it didn't get very far. Maybe synchronizing the client cache on a cluster with many objects did it.