|
vor 5 Jahren | |
---|---|---|
.. | ||
.gitignore | vor 5 Jahren | |
BUILD | vor 5 Jahren | |
Dockerfile | vor 5 Jahren | |
Makefile | vor 5 Jahren | |
README.md | vor 5 Jahren | |
VERSION | vor 5 Jahren | |
main.go | vor 5 Jahren | |
tcp.go | vor 5 Jahren |
Network services with heavy load will cause "connection reset" from time to time. Especially those with big payloads. When packets with sequence number out-of-window arrived k8s node, conntrack marked them as INVALID. kube-proxy will ignore them, without rewriting DNAT. The packet goes back the original pod, who doesn't recognize the packet because of the wrong source ip, end up RSTing the connection.