Skip to content

fix(engine): the bind host configurable (CORVUS_BIND_HOST) - #49

Merged
tmttodd merged 4 commits into
mainfrom
fix/bind-host
Oct 19, 2026
Merged

tmttodd merged 4 commits into
mainfrom
fix/bind-host

Conversation

@tmttodd

@tmttodd tmttodd commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

The deployed engine's Service and probes target the pod IP; the loopback bind refuses them (the pod's Completed/exit-0 signature). The fix: CORVUS_BIND_HOST-configurable, the loopback default preserved.

Claude Code (agent) added 4 commits October 19, 2026 06:29
…e deployed Service and probes need a non-loopback bind

The v1-local loopback default (127.0.0.1) was correct for the in-process
adapter posture but unreachable for the k8s deployment: the Service and
the probes target the pod IP, which the loopback bind refuses
('connect: connection refused', the pod's Completed/exit-0 signature).
The default stays 127.0.0.1 (the local posture is unchanged); the
deployment sets CORVUS_BIND_HOST=0.0.0.0 in the manifest.
…02/F811/F821 cleaned after the bind-host edit
…y before the first-party, the corvus imports alphabetized
@tmttodd
tmttodd merged commit 941c20c into main Oct 19, 2026
2 checks passed
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