ayurishchevandClaude Sonnet 5.5
abbee9a08a
control-api is hosted outside the cloud and validators reach it directly,
so it sees the floating IP as the connection's source address. New open
route GET /api/v1/agents/{id}/observed-ip returns that address (taken only
from the TCP peer; forwarding headers are ignored so a validator cannot
forge it).
The agent gets self_check.methods, a priority-ordered list of ip_echo
(unchanged) and control_api; the default stays [ip_echo]. The self-check
passes when any method confirms the address; the next method is tried on
no answer and on a mismatch. Each method has its own timeout so a hung
first method cannot starve the fallback, and control_api uses a new TCP
connection per call (a connection opened before the floating IP was
attached would keep reporting the old address).
Also: docker agent template/env, example config, docs, plan in
docs/changes, e2e script switch E2E_SELF_CHECK_METHODS, rebuilt
bin/control-api and bin/validator-agent.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
16 lines
587 B
Cheetah
16 lines
587 B
Cheetah
validator_id: "${VALIDATOR_AGENT_VALIDATOR_ID}"
|
|
control_api_url: "${VALIDATOR_AGENT_CONTROL_API_URL}"
|
|
poll_interval_seconds: ${VALIDATOR_AGENT_POLL_INTERVAL_SECONDS}
|
|
|
|
self_check:
|
|
timeout_seconds: ${VALIDATOR_AGENT_SELF_CHECK_TIMEOUT_SECONDS}
|
|
methods: ${VALIDATOR_AGENT_SELF_CHECK_METHODS}
|
|
|
|
checks:
|
|
https_timeout_seconds: ${VALIDATOR_AGENT_HTTPS_TIMEOUT_SECONDS}
|
|
icmp_timeout_seconds: ${VALIDATOR_AGENT_ICMP_TIMEOUT_SECONDS}
|
|
icmp_count: ${VALIDATOR_AGENT_ICMP_COUNT}
|
|
ssh:
|
|
enabled: ${VALIDATOR_AGENT_SSH_ENABLED}
|
|
timeout_seconds: ${VALIDATOR_AGENT_SSH_TIMEOUT_SECONDS}
|