Skip to content

KubeScape Operator getting OOMKilled #382

Open

Description

@Archisman-Mridha

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"}

Activity

  1. Archisman-Mridha commented on Jun 11, 2026

    @Archisman-Mridha
    Author

    It has something to do with these values :

    capabilities:
      scanEmbeddedSBOMs: enable
    
      runtimeDetection: enable
      malwareDetection: enable
    
      continuousScan: enable
    
      manageWorkloads: enable
      syncSBOM: enable
    
    alertCRD:
      installDefault: true
    
    serviceScanConfig:
      enabled: true

    It works if I just do :

    helm repo add kubescape https://kubescape.github.io/helm-charts/ ; helm repo update ; helm upgrade --install kubescape kubescape/kubescape-operator -n kubescape --create-namespace --set clusterName=`kubectl config current-context` --values ./kubescape/values.yaml
  2. Archisman-Mridha commented on Jun 11, 2026

    @Archisman-Mridha
    Author

    Yeah, enabling anything other than configuration.continuousScan: enable breaks the installation.

    I also tried with the latest version of KubeScape Operator container image.

  3. moved this to Accepted in Kubescapingon Jun 19, 2026
  4. matthyx commented on Jun 19, 2026

    @matthyx
    Contributor

    @Archisman-Mridha how big is your cluster? How many pods and other resources?

  5. moved this from Accepted to Needs Information in Kubescapingon Jun 19, 2026
  6. Archisman-Mridha commented on Jun 19, 2026

    @Archisman-Mridha
    Author

    Not too big. We have got 3 nodes : each with 64GB RAM. And I see 410 pods in total currently.

  7. MihaiB-dev commented on Jun 19, 2026

    @MihaiB-dev

    Got the same issue with this setup:

    capabilities:
          configurationScan: enable
          nodeScan: disable
          continuousScan: enable
          vulnerabilityScan: enable
          relevancy: disable
          runtimeObservability: disable
          networkPolicyService: disable
          runtimeDetection: disable
          malwareDetection: disable
          nodeProfileService: disable
          seccompProfileService: disable
          prometheusExporter: enable

    There are ~1200 resources, which is in the range of the documentation. https://kubescape.io/docs/install-operator/#enabling-capabilities

  8. Archisman-Mridha commented on Jul 9, 2026

    @Archisman-Mridha
    Author

    Ping

  9. asifulhaque786 commented on Sep 4, 2026

    @asifulhaque786

    ping facing the same issue

  10. matthyx commented on Sep 4, 2026

    @matthyx
    Contributor

    @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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    • Status
      Needs Information

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions