Add CSv3 cluster operations doc (add-node, resize, cordon, drain)#17
Draft
lvangool wants to merge 1 commit into
Draft
Add CSv3 cluster operations doc (add-node, resize, cordon, drain)#17lvangool wants to merge 1 commit into
lvangool wants to merge 1 commit into
Conversation
CSv3 (K3s) had no customer-facing docs for day-to-day cluster operations; only CSv2/Maestro equivalents existed. A trial customer on HS #33547 was blocked trying to resize, drain, and add nodes. Adds build-and-config/3/cluster-operations.mdx documenting all four operations, including the dashboard-only nature (no cx/API), async timeline behaviour, preconditions (healthy control-plane for cordon/drain; replication guards for scale-down), the lack of in-place vertical resize, and the exact error strings the platform surfaces. All behaviours verified against central source. Linear: SUP-1009 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
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
build-and-config/3/cluster-operations.mdxdocumenting the four CSv3 (K3s) cluster operations:Cloud 66 cannot connect to at least one of your stack servers...,Cannot fetch agent_join_token..., etc.) and the "failed scale-ups don't auto-retry" caveat.kubectl cordonvia the dashboard, 5-min timeout, healthy-control-plane precondition.kubectl drainvia the dashboard, 30-min timeout, PDB/DaemonSet semantics, and timeout troubleshooting.A prominent Callout notes all four are dashboard-only (no
cxcommand, no public API) and that customers can drop tokubectlwith a downloaded kubeconfig.Why
CSv3 had zero customer-facing docs for these operations — only CSv2/Maestro equivalents. A trial customer on HS #33547 was blocked: "unable to figure out how to resize the cluster, couldn't determine the correct procedure to drain... adding to the cluster repeatedly errored without clear guidance."
Verification
Every behaviour, precondition, and error string was verified against central source code (
server_pool.rb,csv3_k3s_clusters/cluster_action_utils.rb,domain/services/csv3/server.rb,operations/services/csv3/server/{drain,cordon}.rb,clusters_controller.rb,clusters/pools_controller.rb) rather than written from assumption.Linear
Test plan
yarn validate:mdxpasses/3/) docs; tables and Callouts displaymainbefore merge (code can drift)🤖 Generated with Claude Code