updates to nats cluster configuration and scripts
Some checks failed
offline / test (push) Has been cancelled
Some checks failed
offline / test (push) Has been cancelled
This commit is contained in:
parent
d0dceae4d0
commit
123e040253
1 changed files with 147 additions and 1 deletions
|
|
@ -17,7 +17,14 @@ Cluster name: `verae`. Client URL:
|
|||
nats://10.10.10.21:4222,nats://10.10.10.22:4222,nats://10.10.10.23:4222
|
||||
```
|
||||
|
||||
**Not** on `vmbr0`. **Not** `0.0.0.0`. Host lab NATS on `127.0.0.1:4222` is left running so current keep/fleet/middleware stay up until you cut over.
|
||||
**Cluster routes (`:6222`) and hub leaf (`:7422`) stay on `vmbr1`.** A **token-gated public client edge** on NS1 forwards to that hub:
|
||||
|
||||
```text
|
||||
nats://<token>@70.88.205.138:4222
|
||||
wss://nats.zapier.georgelambert.org # WebSocket (CONNECT with the same token)
|
||||
```
|
||||
|
||||
Token file on NS1: `/etc/nats/public-edge.token`. Enable/recreate: `bash scripts/expose-public.sh`. Do **not** publish `:6222` or `:8222`. Internal clients keep using the three `10.10.10.21–23` URLs (no token).
|
||||
|
||||
```bash
|
||||
# on NS1 (the Proxmox host)
|
||||
|
|
|
|||
Loading…
Reference in a new issue