Skip to content

[docs] docs: simplify Cluster Stability Check section in architecture.mdx#4648

Open
github-actions[bot] wants to merge 1 commit intomainfrom
docs/unbloat-architecture-376d5507ff133768
Open

[docs] docs: simplify Cluster Stability Check section in architecture.mdx#4648
github-actions[bot] wants to merge 1 commit intomainfrom
docs/unbloat-architecture-376d5507ff133768

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 8, 2026

Summary

Removes implementation-level details from docs/src/content/docs/architecture.mdx that are too granular for an end-user architecture page.

Bloat removed

  • Specific stability check threshold counts (3 vs 5 consecutive checks per distribution)
  • Specific timeout values (2-minute, 3-minute)
  • Internal implementation detail about a "busybox pod" used for Cilium in-cluster connectivity testing
  • Implementation-specific note about K3s/K3d race condition causes and webhook registration

What's preserved

  • The two-phase component installation concept
  • The fact that a Cluster Stability Check runs before GitOps engines
  • The three aspects of the check (API health, DaemonSet readiness, Cilium connectivity) — at a user-relevant level
  • The diff service update impact classification

Why this is bloat

These are implementation internals that belong in CONTRIBUTING.md, not in an end-user architecture page. The page already explicitly references CONTRIBUTING.md for "contributor-level internals (package layout, internal APIs, source structure)". This change aligns the content with that stated scope.

Line count: 174 → 168 lines (6 lines removed from the stability check section)

Generated by Daily Docs · ● 2.7M ·

Remove implementation-level details (specific threshold counts, timeouts,
busybox pod internals) from the end-user architecture page. These details
belong in CONTRIBUTING.md. The key concepts (two-phase installation, stability
check before GitOps) are preserved at a level useful to advanced users.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 8, 2026 10:58
@github-actions github-actions Bot review requested due to automatic review settings May 8, 2026 10:58
@github-project-automation github-project-automation Bot moved this to 🫴 Ready in 🌊 Project Board May 8, 2026
@devantler devantler marked this pull request as ready for review May 8, 2026 14:26
@devantler devantler self-requested a review as a code owner May 8, 2026 14:26
Copilot AI review requested due to automatic review settings May 8, 2026 14:26
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR simplifies the “Cluster Stability Check” portion of the Architecture documentation to keep the page user-focused and avoid implementation-level specifics.

Changes:

  • Condenses the “Cluster Stability Check” description by removing specific thresholds/timeouts and internal mechanics.
  • Simplifies the “Detection and Updates” paragraph to a higher-level explanation of how installed components are identified.

### Detection and Updates

The detector service identifies installed components by querying Helm release history and the Kubernetes API, with additional checks against the Docker daemon where needed. It determines the active distribution, provider, and cluster name from the current kubeconfig context, and distinguishes KSail-managed GitOps resources from unrelated ones so it does not interfere with external GitOps setups.
KSail detects installed components by querying Helm release history and the Kubernetes API, and determines the active distribution, provider, and cluster name from the kubeconfig context. It distinguishes KSail-managed GitOps resources from unrelated ones to avoid interfering with external GitOps setups.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 🫴 Ready

Development

Successfully merging this pull request may close these issues.

1 participant