remove the swarm wireguard mesh; tombstone its options
This commit is contained in:
parent
fbfc6f392a
commit
adc61c9043
1 changed files with 330 additions and 1068 deletions
|
|
@ -522,10 +522,9 @@ in
|
|||
Open {option}`services.hyperhive.swarm.nats.port` in the host firewall
|
||||
on every interface, so hives on other hosts can reach the queue on
|
||||
this host's LAN or public address. Off by default: the port is
|
||||
otherwise open only on the agent bridge and, when this host is on the
|
||||
mesh, on `wg-hive`.
|
||||
otherwise open only on the agent bridge.
|
||||
|
||||
⚠️ This exposes the queue beyond the tunnel. The server binds every
|
||||
⚠️ This exposes the queue beyond the agent bridge. The server binds every
|
||||
address, so the firewall is the only thing this option changes. What
|
||||
protects the port is the queue itself: TLS is required, and
|
||||
`auth_callout` refuses every client it cannot identify. Whether that
|
||||
|
|
@ -846,8 +845,8 @@ in
|
|||
# TLS required on the client port: a server with a `tls`
|
||||
# block advertises `tls_required` and refuses a client that
|
||||
# does not upgrade. No `allow_non_tls`, which would keep the
|
||||
# plaintext path open across the mesh. The 2s timeout is for
|
||||
# a handshake that crosses the mesh; upstream's 0.5s is sized
|
||||
# plaintext path open on the network. The 2s timeout is for
|
||||
# a handshake that crosses the network; upstream's 0.5s is sized
|
||||
# for a LAN.
|
||||
tls = {
|
||||
cert_file = tlsCertPath;
|
||||
|
|
|
|||
Loading…
Reference in a new issue