Repository navigation
Commit e47b29e
authored
deploy: promote balanced node disks to production (#1740)
Promote the 50 GB `pd-balanced` node boot disks from #1739 through the
existing production workflow while retaining registry application image
`1.8.4`. This comment-only change to `deploy/Pulumi.gcpProd.yaml`
deliberately triggers that workflow on merge. The two-node pool retains
`e2-standard-2` machines and uses surge upgrades with one extra node and
zero unavailable nodes.
Staging rollout succeeded:
https://github.com/modelcontextprotocol/registry/actions/runs/40243009855.
Verified both original nodes were replaced with Ready nodes whose actual
boot disks are 50 GB `pd-balanced`. All four original persistent volumes
retain their identities, volume handles and sizes, and both PostgreSQL
clusters recovered. Every active workload is ready; the two registry
replicas are on different nodes, and registry/ingress containers have
zero restarts. Health, listing and name-search checks returned HTTP 200
in about 0.6 seconds; a fresh unique search also returned HTTP 200.
**Allow for a multi-minute database interruption when merging.** During
staging replacement, registry PostgreSQL was unready from 23:16:45 to
23:20:29 UTC on October 25 (3m44s), including its configured 180-second
smart-shutdown timeout before disk reattachment/startup. This is an
observed staging duration, not a production guarantee. Grafana
PostgreSQL also moved. The single staging ingress replica caused three
failed health samples during its move; production has two ingress
replicas but still only one instance of each database. `/health` does
not query PostgreSQL, so database readiness was checked separately.
Surge capacity does not provide database HA.
Refreshed production Pulumi preview at `c71e488`, after #1738 deployed,
passed: node-pool boot-disk size/type update, registry deploy-commit
annotation update, recreation of two automatically cleaned-up ingress
admission Jobs, and existing Grafana empty-rule normalization. No Pulumi
resource deletions/replacements or database/persistent-volume changes.
GKE nevertheless replaces the node VMs incrementally. All PR CI checks
passed.
Check the latest successful registry backup when merging; it last
succeeded at 2026-10-25 04:47:13 UTC during preparation. Both projects
have surge quota headroom; actual zonal capacity is established during
provisioning.
After production rollout, verify both nodes have 50 GB balanced boot
disks, all original persistent volumes are retained, both databases
recover, and workloads/API smoke checks pass. Compare disk queues,
ingress restarts and request latency during busy traffic before
concluding that #1252 is resolved.1 parent cfc66cb commit e47b29e
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
| 1 | + | |
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| |||
0 commit comments