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
{{ message }}
Repository navigation
Kubescape flags digest-pinned CronJob images as floating #5982
Kubescape flags CronJobs whose image references carry both the latest tag and an immutable digest. Kubernetes pulls the exact digest. The extra tag creates noise in the posture report and makes genuinely floating references harder to spot.
Steps to Reproduce
Scan a CronJob with an explicit latest tag, an image digest, and its existing pull policy.
Remove the tag while retaining the digest and repeat the same control scan.
Expected Behavior
The CronJobs use unambiguous digest references and continue to receive automated digest updates.
Actual Behavior
The control flags the redundant tag even though the image selection is already immutable.
Acceptance Criteria
Canonicalize the affected CronJob references and preserve their digests, pull policies, and schedules.
Verify scanner behavior, Renovate digest updates, and the rendered workloads.
Deliver through protected GitOps and verify a fresh posture result for the deployed workloads.
Post-merge verification is complete, so this issue can close.
References made canonical:fix(k8s): use direct digest references for scheduled jobs #5983 (merged 2026-11-10) removed the redundant latest tag and kept the digests, pull policies and schedules. All 14 deployed CronJobs that use the curl-jq helper now run it by digest only. None of the cluster's CronJobs uses a :latest@sha256 reference any more.
Fresh posture result: today's Kubescape workload scans (09:23Z, after both merges) evaluated all 62 controls on the affected CronJobs. The image-tag control C-0075 now passes. The only controls still failing are C-0234 (external secret storage) and C-0236 (image signature). Neither is about image tags, so both are outside this issue's scope.
Activity
devantler commentedon Nov 11, 2026
Post-merge verification is complete, so this issue can close.
latesttag and kept the digests, pull policies and schedules. All 14 deployed CronJobs that use the curl-jq helper now run it by digest only. None of the cluster's CronJobs uses a:latest@sha256reference any more.All three acceptance criteria are met.