Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Move two-node HA page to /moonray #1006

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
+3 −7
Open

[Docs] Move two-node HA page to /moonray #1006

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9eaa88d
Move two-node HA to moonray
nhennigan Jan 24, 2025
14c4189
remove from canonicalk8s index
nhennigan Jan 24, 2025
97b700b
Add to moonray index
nhennigan Jan 24, 2025
66c03ea
remove broken links
nhennigan Jan 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/moonray/howto/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ Overview <self>
:titlesonly:
install
networking/index
two-node-ha
```

---
Expand Down
8 changes: 2 additions & 6 deletions docs/src/snap/howto/two-node-ha.md → docs/moonray/howto/two-node-ha.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Two-Node High-Availability with Dqlite
# Two-node High-Availability with Dqlite

High availability (HA) is a mandatory requirement for most production-grade
Kubernetes deployments, usually implying three or more nodes.
Expand Down Expand Up @@ -28,10 +28,9 @@ standby node, allowing access to the latest Dqlite database version.

Additional recovery steps are automated and invoked through Pacemaker.

### Prerequisites:
### Prerequisites

* Please ensure that both nodes are part of the Kubernetes cluster.
See the [getting started] and [add/remove nodes] guides.
* The user associated with the HA service has SSH access to the peer node and
passwordless sudo configured. For simplicity, the default "ubuntu" user can
be used.
Expand Down Expand Up @@ -420,10 +419,7 @@ sudo drbdadm connect r0
[Raft]: https://raft.github.io/
[Distributed Replicated Block Device]: https://ubuntu.com/server/docs/distributed-replicated-block-device-drbd
[Dqlite recovery guide]: restore-quorum
[external datastore guide]: external-datastore
[two-node-ha.sh script]: https://github.com/canonical/k8s-snap/blob/main/k8s/hack/two-node-ha.sh
[getting started]: ../tutorial/getting-started
[add/remove nodes]: ../tutorial/add-remove-nodes
[Pacemaker]: https://clusterlabs.org/pacemaker/
[Corosync]: https://corosync.github.io/corosync/
[Pacemaker fencing]: https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/html/fencing.html
Expand Down
1 change: 0 additions & 1 deletion docs/src/snap/howto/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,6 @@ Set up cluster observability <observability>
Back up and restore <backup-restore>
Refresh Kubernetes Certificates <refresh-certs>
Recover a cluster after quorum loss <restore-quorum>
two-node-ha
Manage upgrades <upgrades>
Set up Enhanced Platform Awareness <epa>
Manage images <image-management.md>
Expand Down
Loading