pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-09-17 11:29:09 +02:00
Code Issues Packages Projects Releases Wiki Activity

HA docs pass 1

Browse Source
This commit is contained in:
Owen
2026-09-11 12:08:41 -04:00
parent aaab1bcaa1
commit 219d0ef2ed
7 changed files with 845 additions and 161 deletions
Download Patch File Download Diff File Expand all files Collapse all files
development/system-architecture.mdx
+2 -2
View File
@@ -34,7 +34,7 @@ You can run the control plane yourself ([self-hosted](/self-host/quick-install))
A **node** is the networking edge of your Pangolin deployment. It terminates inbound traffic from the public internet, manages WireGuard tunnels, and relays client traffic when a direct peer path is unavailable.
On a self-hosted deployment, your Pangolin server runs as a single node by default. [Enterprise clustering](/self-host/advanced/clustering) spreads multiple nodes behind a load balancer with shared database state. On [Pangolin Cloud](/manage/remote-node/understanding-nodes), you can add **remote nodes**: infrastructure you operate that still receives configuration from the cloud control plane.
On a self-hosted deployment, your Pangolin server runs as a single node by default. [Enterprise clustering](/self-host/advanced/clustering/understanding-clustering) spreads multiple nodes behind a load balancer with shared database state. On [Pangolin Cloud](/manage/remote-node/understanding-nodes), you can add **remote nodes**: infrastructure you operate that still receives configuration from the cloud control plane.
Each node runs several cooperating processes:
@@ -51,7 +51,7 @@ The control plane writes certificates, Traefik router definitions, and WireGuard
Required listener ports, firewall rules, and DNS records for a node.
</Card>
<Card title="Clustering for high availability" icon="server" href="/self-host/advanced/clustering">
<Card title="Clustering for high availability" icon="server" href="/self-host/advanced/clustering/understanding-clustering">
Multi-node Enterprise deployments with shared state and failover.
</Card>