Description
I'm trying to deploy KubeScape (Helm chart v1.40.2). And the KubeScape Operator pod is getting OOMKilled. Even if I provide it with 8GB of memory.
Environment
OS: Ubuntu 24.04 LTS
Version: quay.io/kubescape/kubescape:v4.0.8
Steps To Reproduce
Just try to install the specified version of the KubeScape Operator Helm chart.
Actual Behavior
Additional context
Sometimes, instead of getting OOMKilled, it goes into CrashLoopBackOff state with the following KubeScape Operator pod logs :
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"Image version: v0.2.148"}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"credentials loaded","accessKeyLength":0,"accountLength":0}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"service discovery enabled and started with interval: ","interval":"1h0m0s"}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"starting a new service discovery handling"}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"cloud metadata retrieved successfully","cloudMetadata":{"host_type":"kubernetes","hostname":"bm-qa-htz1-kilroy-eu-2836489","instance_id
":"bm-2836489","private_ip":"10.0.1.2","provider":"hetzner"}}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"successfully retrieved ClusterUID","clusterUID":"58e5a730-92ed-463d-a3d9-0434c74d79bd"}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"Waiting for vuln scan to be ready"}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"starting RegistryCommandsHandler"}
{"level":"info","ts":"2026-06-11T12:08:36Z","msg":"Waiting for REST API to receive notifications, port: 4002"}
The node agents also are showing these error logs :
node-agent {"level":"warn","ts":"2026-06-11T12:10:32Z","msg":"ClamAVClient.handleExecEvent - scanning file","error":"dial unix /clamav/clamd.sock: connect: resource temporarily unavailab
le"}
Description
I'm trying to deploy
KubeScape(Helm chartv1.40.2). And theKubeScape Operatorpod is gettingOOMKilled. Even if I provide it with 8GB of memory.Environment
OS:
Ubuntu 24.04 LTSVersion:
quay.io/kubescape/kubescape:v4.0.8Steps To Reproduce
Just try to install the specified version of the
KubeScape OperatorHelm chart.Actual Behavior
Additional context
Sometimes, instead of getting
OOMKilled, it goes intoCrashLoopBackOffstate with the followingKubeScape Operatorpod logs :The node agents also are showing these error logs :