Operator needs a higher memory limit

kedacore / keda-olm-operator

Operator for deploying KEDA Controller on OperatorHub.io/OLM

Apache License 2.0

31 stars 23 forks source link

Operator needs a higher memory limit #162

Closed StevenBarre closed 1 year ago

StevenBarre commented 1 year ago

https://github.com/kedacore/keda-olm-operator/blob/5c02a15ec6ff19ee8aae7d5f71c5fb0b28ea98d0/config/manager/manager.yaml#L34

$ oc -n keda describe pod keda-olm-operator-5467bbb7b9-547p6 | grep -A10 'Last State'
    Last State:     Terminated
      Reason:       OOMKilled
      Exit Code:    137
      Started:      Thu, 03 Nov 2022 14:13:45 -0700
      Finished:     Thu, 03 Nov 2022 14:14:13 -0700
    Ready:          True
    Restart Count:  3
    Limits:
      cpu:     500m
      memory:  500Mi
    Requests:

StevenBarre commented 1 year ago

I was able to edit the Deployment to increase the memory limit. But I assume the OLM might override/reset that at some point.

Memory on startup appears to peak just over 524M ?

zroubalik commented 1 year ago

@StevenBarre make sense, would you mind opening a PR with more appropriate limits?