Ilker ManapandClaude Opus 5.5 43d3c12302 Make a member's own access rules hostssl when the cluster keeps them there ...

A cluster set up before the rules moved into the shared configuration kept
them in each member's config.yml, which the TLS step never looked at — and
then said its remote rules were hostssl. Found on the PoC: plaintext
connections were still accepted.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-04 12:11:05 +02:00

..

config.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

harden.go

Make a member's own access rules hostssl when the cluster keeps them there

2026-10-04 12:11:05 +02:00

hba.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

metrics.go

Set up a replicated store with server init --patroni, and watch it

2026-10-03 20:57:41 +02:00

pgha_test.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

rest_test.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

rest.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

setup.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

status.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00

tlsmove.go

Put etcd and Patroni's API on TLS, and move a running cluster there in maintenance mode

2026-10-04 12:07:17 +02:00