Skip to content

revert: unsupported Serverless NEG backend timeout - #708

Merged
jjcc123312 merged 1 commit into
mainfrom
codex/revert-router-backend-timeout
Aug 13, 2026
Merged

revert: unsupported Serverless NEG backend timeout#708
jjcc123312 merged 1 commit into
mainfrom
codex/revert-router-backend-timeout

Conversation

@jjcc123312

Copy link
Copy Markdown

Problem / evidence

GCP rejected the attempted single-field production update with:

Invalid value for field 'resource.timeoutSec': '3600'. Timeout sec is not supported for a backend service with Serverless network endpoint groups.

The command failed before changing the backend service; production remained unchanged and healthy.

Root cause

newapi-router-backend uses a Serverless NEG for Cloud Run. The backend service exposes a default timeoutSec in describe output, but GCP does not allow configuring that field for this backend type. The effective request timeout is the Cloud Run service timeout, already 3600 seconds.

Scope / validation

Revert PR #707's unsupported Terraform argument. No production resource changed, no router deploy is required, and router.flatkey.ai remains DNS-only so Cloudflare's proxy timeout no longer applies.

…meout"

This reverts commit 11de547, reversing
changes made to ea9a191.
@jjcc123312
jjcc123312 merged commit 976efa7 into main Aug 13, 2026
2 checks passed
@jjcc123312
jjcc123312 deleted the codex/revert-router-backend-timeout branch August 13, 2026 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant