mirror of
https://github.com/netbirdio/docs.git
synced 2026-10-17 02:59:04 +02:00
docs: make the before-and-after table's columns and HA prerequisites explicit
This commit is contained in:
@@ -14,18 +14,18 @@ The [High Availability guide](/selfhosted/maintenance/scaling/high-availability)
|
||||
|
||||
## How the pieces change
|
||||
|
||||
After the installer, one host runs everything. After this guide:
|
||||
The table compares what the installer set up on one host with what you have at the end of this guide:
|
||||
|
||||
| Piece | Installer deployment | High availability deployment |
|
||||
| Piece | What the installer set up | At the end of this guide |
|
||||
|---|---|---|
|
||||
| NetBird server (Management) | One container on node 1 | The same image on every node, with an identical `config.yaml` |
|
||||
| Dashboard | One container on node 1 | One on every node |
|
||||
| TLS and routing | Traefik on node 1 | Your load balancer, in front of every node |
|
||||
| PostgreSQL | A container on node 1 | Your highly available PostgreSQL endpoint |
|
||||
| PostgreSQL | A container on node 1 | A highly available PostgreSQL service you prepare before you begin |
|
||||
| Login data (embedded identity provider) | An SQLite file on node 1 | The same PostgreSQL endpoint |
|
||||
| Signal | Built into the server | A Signal pool behind the load balancer, at the same URL |
|
||||
| Relay | Built into the server | Separate relay instances, one address each |
|
||||
| Redis and NATS | None: one server keeps its cache and messaging in memory | Shared by every node, so they share that state |
|
||||
| Redis and NATS | None: one server keeps its cache and messaging in memory | Redis and a three-node NATS cluster you set up before you begin, shared by every node |
|
||||
|
||||
The example uses these names. Replace them with your own throughout:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user