node-collector pod in pending state

[wangzhihaocom]

Description

I am installing trivy-operator using helm chart version 0.25.0
and the "node-collector" pod is unable to be scheduled in the trivy-system namespace, and always in the pending state as the following

NAME                              READY   STATUS    RESTARTS   AGE
node-collector-88f6f95c-7dbx2     0/1     Pending   0          5m5s


  Type     Reason             Age                   From                Message
  ----     ------             ----                  ----                -------
  Normal   NotTriggerScaleUp  54s (x31 over 5m55s)  cluster-autoscaler  pod didn't trigger scale-up: 1 node(s) didn't match Pod's node affinity/selector
  Warning  FailedScheduling   53s (x2 over 6m7s)    default-scheduler   0/4 nodes are available: 1 Insufficient cpu, 3 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 1 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling.

and when I checked the job, the job is not completed

kubectl get job -n trivy-system
NAME                      STATUS    COMPLETIONS   DURATION   AGE
node-collector-88f6f95c   Running   0/1           10m        10m

Desired Behavior

The node-collector job should be completed and once the job completed, the node-collector pods will be scheduled and then the pod will be gone after

Actual Behavior

The node-collector pod is always in the pending state

Reproduction Steps

1. 
`helm upgrade -i trivy-operator aqua/trivy-operator --namespace trivy-system --create-namespace --version 0.25.0 -f trivy_operator_values.yaml`

Target

Kubernetes

Scanner

Vulnerability

Output Format

None

Mode

None

Debug Output

kubectl get pods -n trivy-system
NAME                              READY   STATUS    RESTARTS   AGE
node-collector-88f6f95c-7dbx2     0/1     Pending   0          5m5s


  Type     Reason             Age                   From                Message
  ----     ------             ----                  ----                -------
  Normal   NotTriggerScaleUp  54s (x31 over 5m55s)  cluster-autoscaler  pod didn't trigger scale-up: 1 node(s) didn't match Pod's node affinity/selector
  Warning  FailedScheduling   53s (x2 over 6m7s)    default-scheduler   0/4 nodes are available: 1 Insufficient cpu, 3 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 1 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling.

and when I checked the job, the job is not completed

kubectl get job -n trivy-system
NAME                      STATUS    COMPLETIONS   DURATION   AGE
node-collector-88f6f95c   Running   0/1           10m        10m

Operating System

ubuntu 22.04

Version

trivy-operator helm chart version 0.25.0

Checklist

• Run trivy clean --all
• Read the troubleshooting

[afdesk]

@wangzhihaocom could you create a new issue here https://github.com/aquasecurity/trivy-operator/issues?
thanks for the report