feat: live HA cluster scaling controller - #1051
Merged
Merged
Conversation
8 tasks
paulocsanz
force-pushed
the
pcs/pg-mgmt-04-template-apply
branch
from
August 7, 2026 21:01
6fe5000 to
ec5862d
Compare
paulocsanz
force-pushed
the
pcs/pg-mgmt-05-cluster-scale
branch
from
August 7, 2026 21:01
f497f21 to
895fd32
Compare
paulocsanz
force-pushed
the
pcs/pg-mgmt-04-template-apply
branch
from
August 7, 2026 21:08
ec5862d to
f395d56
Compare
paulocsanz
force-pushed
the
pcs/pg-mgmt-05-cluster-scale
branch
from
August 7, 2026 21:08
895fd32 to
2715c45
Compare
Ports the dashboard's useScaleHACluster against the CLI's environment-config types: scaling up clones a live sibling's shape (image, decrypted variables, volume mount) into a brand-new service+volume; scaling down removes the highest-numbered nodes, never the primary coordinator; every change restamps the cluster's declared wiring on survivors. Edge nodes scale as plain region replica counts. After committing, the new members' parent links are re-verified: the public patch path silently drops parentServiceId (confirmed live), and the CLI warns loudly instead of letting the orphaned-topology surprise land later. Part 5/8 of the railway postgres pitr/ha/pgbouncer stack.
paulocsanz
force-pushed
the
pcs/pg-mgmt-05-cluster-scale
branch
from
August 7, 2026 21:18
2715c45 to
c415692
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 5/8 of the railway postgres pitr/ha/pgbouncer stack (split out of #1032 for reviewability — see that PR for the full context, live-prod e2e evidence, and the test-postgres-cli harness). Each PR is based on the previous one and is independently green (cargo test/clippy/fmt).
Ports the dashboard's useScaleHACluster against the CLI's environment-config
types: scaling up clones a live sibling's shape (image, decrypted variables,
volume mount) into a brand-new service+volume; scaling down removes the
highest-numbered nodes, never the primary coordinator; every change restamps
the cluster's declared wiring on survivors. Edge nodes scale as plain region
replica counts. After committing, the new members' parent links are
re-verified: the public patch path silently drops parentServiceId (confirmed
live), and the CLI warns loudly instead of letting the orphaned-topology
surprise land later.
Part 5/8 of the railway postgres pitr/ha/pgbouncer stack.