docs: fix residual legend entries and Qdrant diagram accuracy#246
Merged
docs: fix residual legend entries and Qdrant diagram accuracy#246
Conversation
- Remove "KubeBlocks Operator" and "CRD Resource" legend entries left over in 17 diagram components after the management plane section was deleted in the previous commit - Fix QdrantArchitectureDiagram: Qdrant uses per-shard Raft (no single cluster leader), so rename the LEADER pod badge to PEER and add an explanatory note that each shard elects its own replica leader
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
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.
Changes
Residual legend cleanup
Removed "KubeBlocks Operator" and "CRD Resource" legend entries that remained in 17 diagram components after the management plane section was deleted in #243.
Qdrant diagram accuracy fix
Qdrant uses per-shard Raft consensus — there is no single cluster-level leader. The previous diagram showed one pod as "LEADER" which was inaccurate.
pod-leader/badge-leaderCSS classesTest plan
yarn buildpasses with no errors