Skip to content

docs: improvement on observed generation #880

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.

Sign up for GitHub

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
merged 1 commit into from
Jan 28, 2022
Merged

docs: improvement on observed generation #880

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/documentation/features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,8 +198,9 @@ in status) to handle generation filtering in memory. Thus, if an event is receiv
resource is compared with the resource in the cache.

Note that the **first approach has significant benefits** in the situation when the operator is restarted and there is
no cached resource anymore. In case two this leads to a reconciliation of every resource, event if the resource is not
changed while the operator was not running.
no cached resource anymore. In case two this leads to a reconciliation of every resource in all cases,
event if the resource is not changed while the operator was not running. However, in case informers are used
the reconciliation from startup will happen anyway, since events will be propagated by the informer.

## Support for Well Known (non-custom) Kubernetes Resources

Expand Down