Add guidance: when to add a dedicated worker (small Maestro K8s)#19
Draft
lvangool wants to merge 1 commit into
Draft
Add guidance: when to add a dedicated worker (small Maestro K8s)#19lvangool wants to merge 1 commit into
lvangool wants to merge 1 commit into
Conversation
Small Maestro K8s clusters start with a single shared master running both the control plane and application workloads. The HA doc covered multi- master scaling but never the transition point where a single master is overloaded and a dedicated worker should be added. Adds a section to configuring-for-high-availability.mdx with the symptoms to watch for (slow kubectl, scheduling lag, master-node pod evictions, etcd slow-write warnings) and a Callout distinguishing this from a full HA topology. Linear: SUP-993 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds a "Choosing between a shared master and dedicated workers" section to
build-and-config/configuring-for-high-availability.mdxcovering:kubectl/dashboard, scheduling lag, pod evictions on the master, etcd slow-write warnings)Why
On HS #33527 a small-cluster customer (Pixidon) hit this twice on the same stack three weeks apart. The HA doc covered multi-master scaling but said nothing about the single-master → dedicated-worker transition point, which is a recurring question for small-cluster operators.
Scope note
This is intentionally Maestro/CSv2-oriented (the existing HA doc's context). CSv3/K3s cluster operations are covered separately in the new
build-and-config/3/cluster-operations.mdx(SUP-1009). The symptoms described are general K8s health signals; the procedure links to the existing "Adding nodes" section rather than re-documenting it.Linear
Test plan
yarn validate:mdxpasses#adding-nodes-to-an-applicationresolves🤖 Generated with Claude Code