Repository navigation
Release v0.0.147
Summary
- Split
ReadTimeout: 5sintoReadHeaderTimeout: 5s+ReadTimeout: 30s - The previous 5s
ReadTimeoutcovered the full request (headers + body). Node-agent POSTs a full network stream snapshot every interval; on busy nodes the body read was racing with the timeout, causing the server to close the connection before sending a response. Node-agent then loggedcontext deadline exceeded (Client.Timeout exceeded while awaiting headers). ReadHeaderTimeoutkeeps protection against slow-header attacks; the higherReadTimeoutgives body reads enough headroom.
Deploy note: deploy together with the matching
kubescape/node-agentchange that raises the client timeout to 30s.
Test plan
- Verify no
context deadline exceedederrors in node-agent logs after deploying both PRs together - Confirm
/healthzand normal synchronizer flows are unaffected
🤖 Generated with Claude Code