Serving profiling information can leak information or expose the apiserver to possible DoS attacks. Serving on a UDS is more secure though slightly less convenient. One can't use `go tool pprof` directly against the socket since it's not supported, but can either run a proxy to copy from the socket over to http, or use `curl --unix-socket` to download the profile and then use `go tool pprof`. Kubernetes-commit: 667599b0ddfad8ba760d3bbfe006aae0d8f7dec6 |
||
|---|---|---|
| .. | ||
| OWNERS | ||
| debugsocket.go | ||
| doc.go | ||
| flags.go | ||
| index.go | ||
| metrics.go | ||
| openapi.go | ||
| profiling.go | ||
| version.go | ||