Balancer targets receive requests only after their first health check passes
When a balancer has spec.health, each target starts out of rotation: a new target, or every target on a host whose router has just restarted, receives no requests until its first health check passes, which happens within about 100 ms. One passing check is enough, whatever healthyThreshold is. While no target has passed yet, a request waits for the first check result instead of going to every target. If no target passes, requests go to all targets, as before. A target whose first check fails is reported unhealthy immediately.
Same day.
- Render API for AppsThe web service endpoints of Render's REST API are served under /compat/render/v1, so Render API clients and the render CLI manage Apps b…
- Desktops: E2B Desktop APIDesktops now accept E2B's sandbox REST API with its desktop template at /compat/e2b-desktop: set E2B_API_URL to https://<your API host>/c…
- Launch checks on /status.jsonGET https://withruntime.com/status.json now returns launch_checks, one entry per product that launches with the next platform release (Br…
- Upstash QStash schedules API for CronQStash's schedules endpoints are served under /compat/qstash, so the @upstash/qstash client manages Cron jobs by changing only its base U…
- Start action for Dev environmentsPOST /v2/dev-environments/{id}:start starts an environment immediately: a paused environment is woken, and a stopped one starts again fro…
- Cloud Run: gcloud run revisions list --serviceIn the Google Cloud Run Admin API at /compat/google-cloud-run, v1's namespaces.revisions.list now returns a service's revisions when labe…
- Containers: versions, and Cloud Run revisionsGET /v2/containers/{id}/versions returns a container's versions, newest first and paginated with limit (1 to 100, default 20) and cursor.
- Sandboxes: a fork waits for room, as a create doesWhen no server has room for a copy, fork now retries with the same idempotency key for up to two minutes, as create, wake and restart do,…
- Containers: Cloud Run revisions are named, and traffic can be pinned to oneIn the Google Cloud Run Admin API at /compat/google-cloud-run, each version of a Container is a revision named <service>-<version>, such…
- Better Stack TCP monitors keep their typeIn the Better Stack compatibility API, a PATCH that changes a TCP monitor's monitor_type to status, keyword or expected_status_code now r…
- Better Stack TCP monitorsThe Better Stack compatibility API at /compat/betterstack now accepts monitor_type: "tcp" with url (the host) and port, and creates an Up…
- Better Stack expected-status-code monitorsThe Better Stack compatibility API at /compat/betterstack now accepts monitor_type: "expected_status_code" with expected_status_codes (a…
- Browserbase sessions accept keepAlivePOST /compat/browserbase/v1/sessions accepts keepAlive: true (previously 400).
- Containers: a slug addresses a container, and Cloud Run services keep the name requestedContainers accept an optional spec.slug: 1 to 63 lowercase letters, digits and hyphens, starting with a letter and not ending with a hyph…
- Browserbase session list rejects an unknown statusGET /compat/browserbase/v1/sessions returns 400 when status is not one of RUNNING, ERROR, TIMED_OUT, COMPLETED or PENDING (the values are…
- Console: the Sandboxes, Browsers and Desktops lists show every sandbox, wherever it runsFor many accounts the lists showed only sandboxes made before the account moved to Runtime's new servers, and none made since.