-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve MinEventInterval compliance with docs
**Description** In the command line arguments, we see `min-event-sync-interval` as "The minimum interval between two consecutive synchronizations triggered from kubernetes events" In the code, it actually acts a different way. It imposes a certain dealy between syncs. While this is compliant with the "minimum delay between 2 consecutive synchronizations", it has side-effects in case of large delays. In particular, when trying to fine-tune external-dns to match the provider rate-limits. In this case, it may be interesting to restrict the rate of reconciling actions happening by having a high `min-event-sync-interval`, while keeping a low latency for initial events. This would allow to maximise the bulk effect of high change rate while keeping fast enough reaction for isolated changes. **Checklist** - [X] Unit tests updated - [X] End user documentation updated > End user documentation matches the updated behaviour with more > accuracy Change-Id: Ibcea707974a095a2d5861a3974b4c79e5a15b00e
- Loading branch information
Showing
2 changed files
with
45 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters