docs(multizone): add leader and follower information #1537
Closed
Conversation
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
Signed-off-by: slonka <[email protected]>
✅ Deploy Preview for kuma ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| @@ -69,13 +69,28 @@ A multi-zone deployment includes: | |||
| - Send zone ingresses down to zone control plane. | |||
| - Keep an inventory of all data plane proxies running in all zones (this is only done for observability but is not required for operations). | |||
| - Reject connections from data plane proxies. | |||
| - Leader | |||
| - Writes to the store | |||
There was a problem hiding this comment.
But you can also write stuff to a follower, for example PUT request to create a policy can go to any instance
| - Leader | ||
| - Writes to the store | ||
| - Does insights processing | ||
| - Other leader components (CP catalog, gc, subscription finalizer, inter cp server) |
There was a problem hiding this comment.
I feel like this is might be quite cryptic for the users reading this doc.
Same with "insights processing".
| - The **zone control planes**: | ||
| - Accept connections from data plane proxies started within this zone. | ||
| - Receive policy updates from the global control plane. | ||
| - Send data plane proxies and zone ingress changes to the global control plane. | ||
| - Compute and send configurations using XDS to the local data plane proxies. | ||
| - Update list of services which exist in the zone in the zone ingress. | ||
| - Reject policy changes that do not come from global. | ||
| - Leader | ||
| - Writes to the store | ||
| - Runs k8s controllers (pod converter, CNI taint) |
There was a problem hiding this comment.
Global also run this if global is on Kube
Automaat
reviewed
Jan 29, 2024
| - Does insights processing | ||
| - Other leader components (CP catalog, gc, subscription finalizer, inter cp server) | ||
| - Followers | ||
| - Run default components |
There was a problem hiding this comment.
what are default components in this context?
|
Will reopen if this is needed again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Can someone help me fill this out? I always struggle with remembering who connects to whom, what runs on a leader, what runs on followers and what runs on both.
Did you sign your commit? Instructions
Have you read Contributing guidelines?