Discussion : Tester les chemins d'erreur et les délais d'expiration des appels sortants

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

Where a proxy cannot be inserted (UDP, a driver with a fixed address, a sidecar you do not control), the kernel can inject the same faults: `tc qdisc add dev eth0 root netem delay 200ms 50ms loss 1%` adds latency with jitter and loss on an interface, and it works on a container's own interface given `CAP_NET_ADMIN`. For the two connect-time failures in step 1 the firewall distinguishes them precisely: an `iptables ... -j REJECT --reject-with tcp-reset` rule produces 'connection refused' immediately, while `-j DROP` produces silence, which is the connect-timeout case; the difference matters because clients handle the two very differently, and a test that means 'timeout' but gets 'refused' passes for the wrong reason.