To find out what memory is leaking exactly, Skipper has an option to enable the go profiling tools (pprof).
When running Skipper inside of Kubernetes:
-enable-profilewhen starting Skipper
kubectl port-forward skipper-ingress-pzx2b 9911:9911
l= only in original,
c= in both,
r= in original 2)
original = load("goroutine.dump")original2 = load("goroutine2.dump")l, c, r = original.diff(original2)c.show()
The content of
c is a list of all goroutines that are in both dumps. This means that the goroutine is not cleaned up between the dumps.