^{Originally posted by rekha-prakash-maersk June 5, 2025}
Hello,

I have some ~2 TB of of artifacts where we have a weekly scan scheduled to scan all of the images at weekend midnight. I am noticing that the job service using the cpu&memory resources very less until the end of scan(scan takes ~ 2 hours to complete) but suddenly it needs more memory like ~ 2GB but it enters into restart loop as it starts processing the tasks form beginning again when the pod gets started. to recover from this loop, i have been deploying the jobservice again with more memory for requests like 1 or 2GiB.

I like to understand, what is causing this sudden needs for more resources in job service at the end of scan All. how to tackle this going forward ? I don't want to allocate more resources to jobservice by default as it will be an overallocation.

Resource spec:

Min replica : 6
worker per replica : 10

  resources:
    requests:
      memory: 512Mi
      cpu: 100m
    limits:
      memory: 1Gi
      cpu: 1

Any thoughts or guidance on this will be appreciated!