You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The similar job conditions, Complete and SuccessCriteriaMet, are different in the following ways:
* Complete means that all pods completed and either all of them were successful or the Job already had SuccessCriteriaMet=true.
* SuccessCriteriaMet means that the job meets at least one of successPolicies.
So, the job could have both conditions, Complete and SuccessCriteriaMet.
Solution
To resolve this issue @fl0pp5 suggested next solution:
Description
Trivy kubernetes scan gets stuck in Kubernetes v1.31.* (tested for v1.31.1).
Reason
it seems it appears here kubernetes/kubernetes#126067
the docs - Difference between "Complete" and "SuccessCriteriaMet":
Solution
To resolve this issue @fl0pp5 suggested next solution:
https://github.com/aquasecurity/trivy-kubernetes/blob/b070991579cacd7634052dee2e250350d6e493e8/pkg/jobs/runnable_job.go#L68
On v1.31.1
condition.Type == batchv1.JobSuccessCriteriaMet
but we awaitbatchv1.JobComplete
Discussed in #7705
The text was updated successfully, but these errors were encountered: