Repository navigation
docs: edge clusters in Architecture, Deployment Preparation, Install and Operations - #236
Merged
Merged
Conversation
…ployment, operations) One-node edge clusters managed from a central control plane through the operator's managed profile; two-node edge clusters with hub arbitration documented as a preview (sbcli #1458/#1459, operator #712, ultra #206, spdk #76). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-edge-clusters |
Architecture (deployment topologies), Deployment Preparation (edge requirements), Kubernetes installation (deploying edge clusters) and cluster operations each get an edge page that links the generic pages instead of repeating them. No experimental or preview labels; two-node content notes the arbitration support it needs. Two-node 1+1 on two nodes via twoNode in the deployment document (operator #716). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
schmidt-scaled
changed the title
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-edge-clusters |
…tware Requirements - Linux Block Devices: partitions are storage units (at most one per disk, equal sizes recommended, explicit selection by by-partuuid or serial, journal split from the smallest partition, identity parent serial + -part- + PARTUUID); operator discovery proposes whole disks only. - Edge Cluster Requirements page removed; edge deviations are boxes in Hardware Requirements (3 vCPU / 3 GB RAM minimum, devices, independent links for two nodes, hub/edge ports) and Software Requirements (hub, credentials, control plane nodes, two-node OpenShift, remediation). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-edge-clusters |
1 similar comment
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-edge-clusters |
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
3 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.
Edge clusters (one or two storage nodes at an edge site, managed by a central control plane on a hub through the operator's managed profile), documented inside the existing sections. There is no separate menu item and no separate requirements page. Each page covers only what is edge-specific and links the generic pages.
docs/architecture/deployment-topologies/edge-clusters.md(new)docs/architecture/concepts/linux-block-devices.md(changed)docs/deployment-preparation/hardware-requirements.md(changed)docs/deployment-preparation/software-requirements.md(changed)docs/kubernetes/installation/edge-clusters.md(new)docs/kubernetes/operations/cluster/edge-clusters.md(new)Diagram:
docs/assets/images/architecture/edge-clusters.svg./dev/disk/by-partuuid/...or serial (sn configure --lblk --blk-names/--blk-serials), never automatically; a disk and its own partition cannot both be selected; the smallest partition is split into journal and data (--jm-percent, default 3); identity is the disk serial +-part-+ PARTUUID; the operator discovery (enableLogicalBlockDevices) proposes whole disks only.controlplane.local.adminTokenSecretRef), credentials at the edge, control plane nodes for storage, two-node OpenShift (arbiter or fencing), node remediation.spec.cluster.twoNode, monitoring, failure tables, healing, upgrades, troubleshooting incl.GET /api/v2/clusters/{id}/arbitration).No experimental or preview labels. The two-node parts carry a short note that they require two-node arbitration support in the control plane, the Simplyblock Operator, and the storage nodes (sbcli #1458/#1459, simplyblock-operator #712 and #716 on
feature/two-node-ha, ultra #206, spdk #76).Resolved: two-node 1+1 on two storage nodes with the
twoNodedeclaration (operator #716); partitions as devices are documented.TODO before merge (to confirm with engineering):
kubectl expose service simplyblock-webappapi --type LoadBalancer; confirm the recommended production exposure (Route or Ingress with TLS).Quality gate passes for all changed pages, and
mkdocs build --strictreports onlyreference/api/index.md→openapi.json, which is pre-existing on main and generated in CI.🤖 Generated with Claude Code