Skip to content

Fix image tracking for initContainers and CronJob containers#6552

Open
zyzzmohit wants to merge 1 commit intopipe-cd:masterfrom
zyzzmohit:fix/issue-6528-findcontainerimages
Open

Fix image tracking for initContainers and CronJob containers#6552
zyzzmohit wants to merge 1 commit intopipe-cd:masterfrom
zyzzmohit:fix/issue-6528-findcontainerimages

Conversation

@zyzzmohit
Copy link

What this PR does: Updates FindContainerImages to correctly extract and track images from initContainers and CronJob specifications.

Why we need it: Currently, FindContainerImages only traverses spec.template.spec.containers.image. This limitation causes deployments containing initContainers or batch CronJob workloads to have their images completely ignored during tracking and manifest analysis. This PR expands the AST traversal to capture those missing layers.

Which issue(s) this PR fixes: Fixes #6528

Does this PR introduce a user-facing change?:

How are users affected by this change: Image tracking and drift detection will now accurately reflect initContainers and CronJob images, providing a complete view of the deployed workload.
Is this breaking change: No
How to migrate (if breaking change): N/A

…erImages

This commit fixes an issue where 'FindContainerImages' only searched within 'spec.template.spec.containers.image', causing initContainers and scheduled job containers to be left out of image tracking. By traversing 'initContainers' and 'jobTemplate.spec', images in these contexts are now correctly tracked.

Fixes pipe-cd#6528

Signed-off-by: zyzzmohit <mohitray949@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FindContainerImages does not detect images in initContainers and CronJob jobTemplate

1 participant