Add per-rule custom plugin intervals#1320
Conversation
Group rules by their effective invoke interval. Use the global interval when a rule omits its interval. Reject non-positive invoke intervals before scheduler startup. Test grouped cadence, concurrency, and shutdown behavior.
|
Hi @DigitalVeer. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
State that rules with different intervals run on independent schedules. State the concurrency limit and the catch-up behavior. State the rule timeout validation limit.
|
/ok-to-test |
Return a snapshot struct from the test execution recorder. Move the apply-configuration test table into a helper function.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DigitalVeer, hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
Custom plugin rules can set an optional invoke interval and rules without this field will use the global invoke interval.
The scheduler groups rules with equal parsed durations.
Each group runs one synchronized batch for each tick.
Compatibility
The default schedule keeps one shared batch for all rules.
The scheduler creates all tickers before the combined boot batch.
Downstream result handling does not change.
Tests
This PR adds fake-clock tests for the scheduler.
The lifecycle bot closed prior attempts #357 and #358.