Skip to content

Conversation

@edigaryev
Copy link
Collaborator

In the next PR we can add schedule field to the ImagePullJob and an OpenAPI documentation.

See #352.

@edigaryev edigaryev requested a review from fkorotkov as a code owner December 10, 2025 19:45
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines 148 to 152
// Garbage collect orphaned image pulls
for _, imagePull := range imagePulls {
if lo.ContainsBy(imagePull.OwnerReferences, func(ownerReference v1.OwnerReference) bool {
imagePullJob, ok := imagePullJobIndex[ownerReference.Name]
if !ok {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Manual image pulls garbage-collected immediately

The image pull scheduler only retains pulls whose OwnerReferences match an existing ImagePullJob; everything else in this loop goes down the removal path a few lines below. Manually created pulls (POST /imagepulls) have no owner references, so every scheduler iteration treats them as orphaned and deletes them before workers can process them, breaking the direct image pull flow exercised by TestImagePull.

Useful? React with 👍 / 👎.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 995b3c5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants