Skip to content

Lurker terminated with 'OOMKilled' event #2327

@Alon-Katz

Description

@Alon-Katz

🐞 Bug report

Describe the bug

The lurker is failing due to an 'OOMKilled' issue and the resource allocations are hard-coded in the code, which raises the question: why? In heavy production environments, it is unreasonable to be constrained by the following resource limits without any option to increase them:

    Limits:
      cpu:     100m
      memory:  100Mi
    Requests:
      cpu:     20m
      memory:  20Mi

Steps To Reproduce

Run a scan with thousands of findings

Expected behavior

Please either implement a method to allow the increase of resources allocated to the lurker or ensure that it cannot be terminated due to an OOM event.

System (please complete the following information):

secureCodeBox Version/Release:
v4.4.1
Kubernetes Version [command: kubectl version]:
Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.5-eks-5e0fdde

Screenshots / Logs

  containerStatuses:
  - containerID: containerd://f0455a853556f2174458a2320c4d4f5fc68d271b96788a78eff16c67d4dfed02
    image: docker.io/zricethezav/gitleaks:v8.18.2
    lastState: {}
    name: gitleaks
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: containerd://f0455a853556f2174458a2320c4d4f5fc68d271b96788a78eff16c67d4dfed02
        exitCode: 0
        finishedAt: "2024-03-03T10:05:36Z"
        reason: Completed
        startedAt: "2024-03-03T10:04:33Z"
  - containerID: containerd://9ad202c0521385c90259273ef5576289f01ec3bb61d38c4e862a97ad59e98fdb
    image: docker.io/securecodebox/lurker:4.4.1
    lastState:
      terminated:
        containerID: containerd://9ad202c0521385c90259273ef5576289f01ec3bb61d38c4e862a97ad59e98fdb
        exitCode: 137
        finishedAt: "2024-03-03T10:06:04Z"
        reason: OOMKilled
        startedAt: "2024-03-03T10:06:00Z"
    name: lurker
    ready: false
    restartCount: 2
    started: false
    state:
      waiting:
        message: back-off 20s restarting failed container=lurker pod=scan-retry-2f1cf8e1-8bf5-4e7e-a0de-93fe6ac44005-2prlb-4sj5g_scb-scanners(05be3608-393d-437e-8386-89422b52d0c6)
        reason: CrashLoopBackOff  

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions