Skip to content

Conversation

@rockythorn
Copy link
Collaborator

Adds Kubernetes CronJob that runs RhMatcherWorkflow every 6 hours, completing the final manual step in the Rocky Linux advisory automation. Follows the same pattern as the existing apollo-rhworker PollRHCSAFAdvisoriesWorkflow CronJob.

… in advisory generation pipeline

Adds Kubernetes CronJob that runs RhMatcherWorkflow every 4 hours, completing the final manual step in the Rocky Linux advisory automation. Follows the same pattern as the existing apollo-rhworker PollRHCSAFAdvisoriesWorkflow CronJob.
@rockythorn rockythorn requested review from NeilHanlon and mstg December 4, 2025 21:23
Copy link

@elguero elguero left a comment

Choose a reason for hiding this comment

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

Looks sane to me.

Mustafa or Neil should double check.

Copy link
Contributor

@NeilHanlon NeilHanlon left a comment

Choose a reason for hiding this comment

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

This looks great overall, thanks very much @rockythorn ! Follows established patterns, best practices, and sidecar management integration pain I ran into.

A couple operational suggestions to discuss/work in (independent of this PR):

  • Consider adding concurrencyPolicy: Forbid to the CronJob spec -- since the wf has a 12 hour timeout per product, if a job takes >6h we may get overlapping executions leading to a resource exhaustion upstream somewhere (database/cpu)
  • Given the 12 hour activity timeout, we might want to monitor/profile the actual runtime and consider if the schedule needs adjustment. We can watch this post-deployment.
  • Commit message says "every 4 hours" but the code says every 6. Minor nit for posterity so I can't be accused of missing anything ;)

LGTM! 🚀

@brianclemens brianclemens merged commit 33872ac into resf:main Jan 4, 2026
1 check passed
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.

4 participants