Document dedicated master nodes#123
Open
WalBeh wants to merge 1 commit into
Open
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Explain what dedicated master nodes are, when they help, how they are chosen at deploy time (odd quorum, fixed size, spread across AZs), and how they are billed. Link the Custom-plan feature bullet to the new section.
goat-ssh
force-pushed
the
docs/dedicated-master-nodes
branch
from
d9959d4 to
09e39ca
Compare
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
2 participants
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.
What's Inside
Adds a Dedicated master nodes section to the Services reference page,
documenting the feature shipped in cloud-api (crate-operator#845 companion).
It explains what dedicated master nodes are (a separate pool that only manages
cluster state), when they help (larger/busier clusters, strict availability),
how they're chosen (deploy-time, odd quorum of three or five, fixed size,
spread across AZs, independent of data-node scaling), and how they're billed
(additional compute + storage; suspend pauses master compute while master
storage keeps billing).
The Custom-plan card already name-dropped the feature; that bullet now links to
the new section.
Preview
reference/services.md→ new## Dedicated master nodessection (after theDedicated plan's High Availability notes, before Custom).
Highlights
integration is separate cloud-ui work).
Checklist