Skip to content

fix(infra)(#321): aggregator-proxy /health passes through to backend #323

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vrogojin merged 1 commit into from
Jun 8, 2026
Merged

fix(infra)(#321): aggregator-proxy /health passes through to backend #323

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions tests/e2e/local-infra/aggregator-image/proxy/nginx.conf.template
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,11 +38,18 @@ server {
proxy_send_timeout 600s;
}

# Lightweight liveness — short-circuits the backend so the proxy
# itself can fail-fast if nginx is wedged but the backend is fine.
# /health passes through to the backend so callers see the full
# response (status, role, sharding, database details, etc.). The
# proxy's own liveness is implicit — if nginx is up enough to
# forward the request and read the reply, both halves are alive.
# Hiding the backend response behind a static 200 made tools like
# unicity-infra-probe report "degraded" because they couldn't see
# database state.
location = /health {
access_log off;
return 200 '{"status":"ok"}';
default_type application/json;
proxy_pass http://aggregator_backend;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_read_timeout 10s;
}
}