Document TLS between the store's machines, and close section A of the backlog
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
43d3c12302
commit
eb10aee93b
3 files changed
+29
-14
No files matched your search
@@ -152,6 +152,15 @@ promoted within about thirty seconds of the primary being lost, and the
|
||||
control plane follows it by itself. `llmgw ctl status` says who leads; see
|
||||
[deploy/ha](../deploy/ha/README.md) for what it sets up.
|
||||
|
||||
Everything between the machines is TLS, with certificates from the cluster's
|
||||
own authority: PostgreSQL (every remote rule is `hostssl`, and the control
|
||||
plane verifies the member it reaches), etcd (peers and clients, and a client
|
||||
must present a certificate), and Patroni's API, which also asks for a
|
||||
password before a change. A cluster set up by an earlier llmgw is moved to
|
||||
this by running the same command again, on the control plane that holds the
|
||||
authority: etcd is rebuilt on TLS with Patroni in maintenance mode, so
|
||||
PostgreSQL serves throughout and no failover happens.
|
||||
|
||||
Every step looks before it acts. Running it again finishes an install that
|
||||
stopped halfway and changes nothing on one that did not; it never overwrites
|
||||
`server.yaml`, the authority, or an existing account's password.
|
||||
|
||||
Reference in new issue
Block a user