Debugging a TCP socket leak in a Kubernetes cluster
I have read this near four times now. I can&#x27;t really find any sustenance -- it appears to be a advertisement for a product wrapped in a unsolved issue.<p>No mention of lsof, netstat, or tcpdump, the normal tools used for troubleshooting these sort of problems. Without trying to sound to snarky I find it highly concerning that the industry is now working with tools like docker and Kubernties and we some how just throw out the fact that these sit on top of Linux.<p>Not to mention kubelet&#x27;s ability to spot one of many turntables reaching a max still would have not solved this problem -- &quot;Fundamentally, the node was unhealthy&quot; -- is not a proper answer to the problem -- what was done to resolve the memory issue is. That could be increasing the tcp_mem to to support the workload, or finding a faulty user space program who is acting faulty -- all of which we have no clue because no real tools for troubleshooting this were used.<p>I mainly write this gripe because this appears to be a problemtisement, or a blogtisement. A &quot;helpful&quot; but not informative blog simply to provide a way to advertise your companies service at as the final blurb, leaving us with no real solution, resolution or a closing to the mystery of why tcp_mem was higher than expected.