Migration PR 4, Stage 4: load-balancer runbook, executed state, and initial URL-map snapshot#3745
Merged
Merged
Conversation
Gcloud equivalents of every console action for provisioning the global external ALB (EXTERNAL_MANAGED): dual IPv4+IPv6 frontends (the current host serves AAAA via ghs.googlehosted.com, so IPv6 clients exist), DNS-authorized Certificate Manager cert for both hostnames, serverless NEGs for App Engine and Cloud Run in us-central1, backend services with timeout 600 and full request logging, and a URL map pinned to app_engine=100/cloud_run=0 so every future ramp step is a weight edit. Committed before execution per the plan's manual-infra rule; exit gates and full teardown included. The recurring weight-change procedure (export -> diff -> edit -> import -> verify -> commit snapshot) lands in the living operations doc. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timeoutSec and portName are rejected on backend services with serverless NEG backends; the timeout is platform-fixed at 60 minutes (docs-verified), making the planned --timeout=600 both impossible and unnecessary. Old gcloud sets portName unconditionally at create, so the services were created via the Compute REST API with backends inline. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3745 +/- ##
=======================================
Coverage 79.89% 79.89%
=======================================
Files 70 70
Lines 4332 4332
Branches 807 807
=======================================
Hits 3461 3461
Misses 652 652
Partials 219 219 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Summary
Documentation for Stage 4 of the host cutover — the load balancer described here is already provisioned and validated (executed 2026-07-08 with step-by-step authorization; this PR records how, exactly as built).
docs/migration/history/pr4-stage4-load-balancer-runbook.md): gcloud/REST commands for every action, amended with execution reality — reserved IPs recorded (34.117.200.13/2600:1901:0:347b::), and the two serverless-NEG platform constraints discovered mid-execution:timeoutSecis rejected (the LB timeout is fixed at 60 minutes for serverless backends, making the planned--timeout=600unnecessary), andportNameis rejected while older gcloud sets it unconditionally — so backend services were created via the Compute REST API with backends inline.docs/migration/cloud-run-operations.md: export → diff → edit → import → verify → commit snapshot.url-maps importreplaces the whole resource, so the committed snapshot is what makes editing safe.docs/migration/urlmap/20260708T182458Z-lb-api.yaml) at app_engine=100 / cloud_run=0 — the diff anchor for every future ramp step.Exit gates (all passed 2026-07-08)
ACTIVE, both hostnames authorized (~8 min after the Squarespace CNAMEs)curl --resolvevia the LB IP: 200 in 0.40s withX-PolicyEngine-Backend: app_engine— over IPv4 and IPv6backend_service_name: bs-app-engine(note for Stage 6: this project'shttp_load_balancerlogs also containaef-default-*entries from App Engine's own internal serving — monitoring must filter onbs-*)No public traffic touches the LB: DNS for
api.policyengine.orgstill points at App Engine, and nothing resolves to the LB IPs until Stage 5'sapi-lbrecord.🤖 Generated with Claude Code