fix(gcp): expose read-API /healthz and accept deny-502 in native proof
Merged
KH
1h ago+27+27+01234567890123456789-4-4-0123456789
Summary
- Native umbrella edge routed every unmatched history-host path to the selector-less deny Service (Google answers 502), but
verify-public.shrequires 2xx onhistory.<base>/healthz. Adds an Exact/healthzroute to the native read edge — the same probe the GCE health check already uses. public.history_internal_deniedexpected 404/403 but the deny backend answers 502; sibling deny cases already accept 502 asedge_denied. Made this case consistent. The isolation property (internal paths never reach the read API) is unchanged.
Validation
helm templaterenders the new Exact/healthzrule.- Live edge confirmed:
/healthz→ 502 before the change,public.history_internal_deniedwas the only verifier gap remaining (verifier was 15/17, the other being this case and the history health URL).
Generated with Devin
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes two live-proof failures on the native GKE edge so verify-public.sh passes.
- Adds an Exact
/healthzroute to the native read edge; previously the umbrella routed it to the selector-less deny Service and Google answered 502. - Accepts 502 in
public.history_internal_deniedsince the deny backend answers 502; internal paths still never reach the read API, so the isolation property is unchanged. - Bumps
agent-relayto0.6.52, registers it as the current release row, and marks0.6.51as planned.