-
Notifications
You must be signed in to change notification settings - Fork 1.2k
📖 Improve docs for manager.Options.SyncPeriod #1232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
k8s-ci-robot
merged 3 commits into
kubernetes-sigs:master
from
dlipovetsky:explain-syncperiod
Mar 3, 2021
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -139,6 +139,25 @@ type Options struct { | |
// value only if you know what you are doing. Defaults to 10 hours if unset. | ||
// there will a 10 percent jitter between the SyncPeriod of all controllers | ||
// so that all controllers will not send list requests simultaneously. | ||
// | ||
// This applies to all controllers. | ||
// | ||
// A period sync happens for two reasons: | ||
// 1. To insure against a bug in the controller that causes an object to not | ||
// be requeued, when it otherwise should be requeued. | ||
// 2. To insure against an unknown bug in controller-runtime, or its dependencies, | ||
// that causes an object to not be requeued, when it otherwise should be | ||
// requeued, or to be removed from the queue, when it otherwise should not | ||
// be removed. | ||
// | ||
// If you want | ||
// 1. to insure against missed watch events, or | ||
// 2. to poll services that cannot be watched, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Depending on the use case, this can be better served by a channel watch and a background goroutine, but that's definitely the more advanced version :) |
||
// then we recommend that, instead of changing the default period, the | ||
// controller requeue, with a constant duration `t`, whenever the controller | ||
// is "done" with an object, and would otherwise not requeue it, i.e., we | ||
// recommend the `Reconcile` function return `reconcile.Result{RequeueAfter: t}`, | ||
// instead of `reconcile.Result{}`. | ||
SyncPeriod *time.Duration | ||
|
||
// Logger is the logger that should be used by this manager. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.