capo misc failing on neuvector on workload cluster

Job #14638194346 failed for 0c4f60d6:

We have seen many timeout for neuvector unit in CI jobs.

After analyzing the failure in the above job, we observed that there is almost 5min between the first Neuvector pod ready and the last one.

name: neuvector-enforcer-pod
      ready: true
      resources:
        limits:
          cpu: "2"
          memory: 2792Mi
        requests:
          cpu: 100m
          memory: 2280Mi
      restartCount: 0
      started: true
      state:
        running:
          startedAt: "2026-06-01T19:17:28Z"

name: neuvector-controller-pod
      ready: true
      resources:
        limits:
          cpu: 400m
          memory: 2792Mi
        requests:
          cpu: 100m
          memory: 2280Mi
      restartCount: 0
      started: true
      state:
        running:
          startedAt: "2026-06-01T19:22:46Z"

/cc @frmenguy

Edited by François-Régis Menguy