Skip to content

fix architecture-and-internals document #1080

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
Mar 24, 2022
Merged

fix architecture-and-internals document #1080

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
2 changes: 1 addition & 1 deletion docs/documentation/architecture-and-internals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ A typical workflows looks like following:
2. In the event processor the related `CustomResource` is read from the cache based on the `ResourceID` in the event.
3. If there is no other execution running for the custom resource, an execution is submitted for the executor (thread
pool) .
4. Executor call EventDispatcher what decides which method to execute of the reconciler. Let's say in this case it
4. Executor calls ReconcilerDispatcher which decides which method to execute of the reconciler. Let's say in this case it
was `reconcile(...)`
5. After reconciler execution the Dispatcher calls Kubernetes API server, since the `reconcile` method returned
with `UpdateControl.updateStatus(...)` result.
Expand Down