Repository navigation
docs(superpowers): GCP parity design and plan - #2120
Merged
Merged
Conversation
The next rebuild runs on GCP (owner, 2026-09-29): gcp-0 becomes a GCP-only platform that runs the agent factory, and AWS keeps only Route53, the AWS-GCP federation, the S3 state bucket and the OpenBao lineage. The plan salvages the OpenBao Stage 2 port to GCP verified live on 2026-09-11 (never merged), moves ZITADEL's primary to GCP, adds a GKE Sandbox pool, per-cloud issuers for agent-router and octo-sts, gcp-0 agent umbrellas and a cloud-shape render gate. Platform fixes (G-0..G-3) can merge on their own; G-4 flips the primary; G-5 stacks on H-1.
Contributor
🔍 Rendered manifest diff — this PR vs
|
The independent review found 4 Critical and 11 Important issues; all are fixed in the plan and spec, with the owner's decisions of 2026-09-29: the freshly generated ZITADEL PAT always wins over a stored one, the old GCP OpenBao lineage is restored, G-0..G-3 merge ahead when green while G-4 (primary cloud) stays on integration, and a guarded GCP teardown sweep deletes leftover load-balancer resources. Also carries H-1's final-review amendments to the SP2 plan: Task 0.5.14 moves integration's package pin to an artifact-publishing pre-release and checks run logs for GitHub tokens, Task 3.8 lists the MCP allowlist test, P39 names its residual reads, and Phase 7 re-points runbook URLs.
Applies the GCP parity plan's cross-plan edits: SP2 retargets its live gates to gcp-0, adds TLS on the room broker's bridge listener (GP-18, no WireGuard on gcp-0) and the gcp-0 hairpin ruling; the observability plan stacks O-1 on GCP parity G-5 and runs its live gates on gcp-0.
…, SP2 and SP3 plans GCP parity plan and spec: - PR map status (G-0..G-3 merged, G-4 draft on main, G-5 in progress) and the H' rebase-onto-main base for G-2/G-3 - W1-W5 in tasks 6.1-6.7; the runbook retarget moves to Phase 7 (Task 7.2) - Z1 gVisor toleration policy, Z2 socketLB as a guard, Z3 metadata server by CIDR; task 6.3's code as committed - Rulings R, U and AB; Phase 8 open live items and new checks - A "Rulings applied during execution" index SP2 plan and spec: - P33 lifted for agent-platform; AP-0 merged; no package-visibility step - Ruling Y: tasks 1.3/1.4 carry the landed schema and store; Appendix C - Rulings AC/AD: internal/app, OTel metrics, httpx, injected clock, server timeouts, TLS reload across tasks 1.6, 1.9, 1.11, 1.12 and phases 2-6 - GP-18 applied in tasks 1.9, 1.11, 1.14 and the live curls; CRD bounds; atlasSchema.ref after AP-1; /api/rooms json tags; Phase 7 gaps SP3 plan: the merge gate lands on GCP's management stack too.
The rooms plan's three conflicts are unions: main's R04 internal-egress gate, its internal-run OWNER row and the 7.0 UX-fixes node, beside this branch's 2026-09-29 rulings and OWNER rows. Task 7.2 gains a status note: the agent-platform P33 lift was not used past AP-0, so AP-1…AP-6 still merge in the wave.
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
1 participant
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.
🔍 docs
📝 Summary
The next rebuild runs on GCP (owner, 2026-09-29): gcp-0 becomes a GCP-only platform that runs the agent factory, and AWS keeps only Route53, the AWS↔GCP federation, the S3 state bucket and the OpenBao lineage. Text only.
worktree-openbao-stage2-gcpac62abf2), aligned withmain.main.primary_cloudtogcp(the owner decides when).An independent review is running; its fixes will land on this PR.
2026-09-29 execution rulings
Each plan now ends with a Rulings applied during execution (2026-09-29) table, and the task text carries each ruling in place.
main; G-5 in progress). W1–W5 are in tasks 6.1–6.7, and the runbook retarget moves to Phase 7 (new Task 7.2). Also:socketLB.hostNamespaceOnlyis kept as a guard, plus a negative Gateway check from two nodes.atlasSchema.refafter AP-1, the/api/roomsjson tags, and the Phase 7 release gaps.