feat: regional API MIG#2490
Conversation
Introduces an `api-cluster` module that provisions the API nodepool as a
regional MIG (BALANCED distribution) in parallel with the existing zonal
`google_compute_instance_group_manager.api_pool`. Load balancer backends are
unchanged and still point at the zonal pool; the regional pool is staged for
a follow-up cutover.
Also drops the `datacenters = ["${gcp_zone}"]` constraint from the
docker-reverse-proxy job so it can schedule on API nodes regardless of zone
once the regional MIG is live.
Backs the four API-facing LB backends (session, api, docker-reverse-proxy, ingress) with both the zonal and regional instance groups so traffic is served by both pools during cutover. Also parameterizes the regional MIG's surge/unavailable counts off the actual zone count in the region (mirrors the server pool pattern), instead of hardcoding 3.
PR SummaryMedium Risk Overview Reviewed by Cursor Bugbot for commit c7af58a. Bugbot is set up for automated code reviews on this repo. Configure here. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
jakubno
requested review from
sitole
and removed request for
ValentaTomas and
dobrac
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 875cf02. Configure here.
sitole
left a comment
sitole
left a comment
There was a problem hiding this comment.
Lgtm please move api cluster module to be reusable
Match the layout convention used by provider-aws/modules so the API nodepool module lives alongside its scripts and is reusable across envs without further state migration.
3 participants
datacenters = ["${gcp_zone}"]constraint from the docker-reverse-proxy