Repository navigation
Open
Labels
bugSomething isn't workingSomething isn't working
Description
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"}
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
- StatusShow more project fieldsNeeds Information
Activity
Archisman-Mridha commentedon Jun 11, 2026
It has something to do with these values :
It works if I just do :
Archisman-Mridha commentedon Jun 11, 2026
Yeah, enabling anything other than
configuration.continuousScan: enablebreaks the installation.matthyx commentedon Jun 19, 2026
@Archisman-Mridha how big is your cluster? How many pods and other resources?
Archisman-Mridha commentedon Jun 19, 2026
Not too big. We have got 3 nodes : each with 64GB RAM. And I see 410 pods in total currently.
MihaiB-dev commentedon Jun 19, 2026
Got the same issue with this setup:
There are ~1200 resources, which is in the range of the documentation. https://kubescape.io/docs/install-operator/#enabling-capabilities
Archisman-Mridha commentedon Jul 9, 2026
Ping
asifulhaque786 commentedon Sep 4, 2026
ping facing the same issue
matthyx commentedon Sep 4, 2026
@asifulhaque786 can you try with the latest chart? https://github.com/kubescape/helm-charts/releases/tag/kubescape-operator-1.40.4 we made some improvements on resources fetch.
Can you also give me more details about your setup?
fix(kubescape): disable service scan by default