Documentation
¶
Overview ¶
Command udsecho is the UDS-serving test workload for the proposal 034 e2e harness (e2e/uds.sh): a tiny HTTP server that listens ONLY on a Unix domain socket inside its pod's emptyDir and never binds a TCP port.
That "never binds TCP" property is what makes the harness's assertions meaningful: the mesh advertises the pod at pod_ip:18008 and delivers over the socket, so any 200 a client sees proves the node proxy dialed the pipe. If UDS delivery silently fell back to TCP loopback, nothing would be listening, the delegated-liveness probe would fail, and the endpoint would stay unpromoted.
It answers 200 on every path (the delegated-liveness probe uses GET / with Host: localhost over the same socket) with a one-line body naming the socket and the pod, so the harness can tell which workload served a request.