Repository navigation
Conversation
Add a page under docs/v3.7/learning describing how client requests flow through an etcd cluster: writes handled by the leader, writes forwarded from a follower, and linearizable vs serializable reads. The diagrams are copied from the etcd-io/etcd repository (Documentation/etcd-internals/diagrams). Fixes etcd-io#643 Signed-off-by: Jack Byers <jzbyers@gmail.com>
Copy the new request flow page and its diagrams from docs/v3.7 so the page carries forward to the next docs version. Ref etcd-io#643 Signed-off-by: Jack Byers <jzbyers@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jzbyers The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @jzbyers. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Oh, hey, thanks! It'll take us a bit to review this one for obvious reasons. We'll let you know. |
|
/ok-to-test |
|
So, one thing we'll need to be able to do with this is to keep the diagrams up to date. I'm trying to figure out what an appropriate location would be to store the prompts for generating these images, so that we can repeat the process for future versions of the documentation. |
Addresses #643, a request to add docs that describe a request's flow through etcd.
Scope: add request flow doc for v3.7 and v3.8. I can copy the docs over to older versions if desired.
AI disclosure: I used Claude Opus 4.8 to scan through the rest of the docs, find relevant images we could re-use to describe the request flows, and use terminology consistent with the rest of the docs.