Implemented pprof

[ellistarn]

1. Issue, if available:

2. Description of changes:
😮😮😮😮😮
😮😮😮😮😮
😮😮😮😮😮

3. How was this change tested?

4. Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: link to issue
• No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[netlify]

✅ Deploy Preview for karpenter-docs-prod canceled.

Name	Link
🔨 Latest commit	cd5f75f
🔍 Latest deploy log	https://app.netlify.com/sites/karpenter-docs-prod/deploys/62acfd6a08ea4b00082a50b1

[dewjam]

Do we want the Profiling endpoint to be enabled by default? Or should we add a command line flag to explicitly enable Profiling similar to kube-controller-manager?

[chrisnegus]

I added a couple of small suggestions to the one doc file.

[ellistarn]

@dewjam

Do we want the Profiling endpoint to be enabled by default? Or should we add a command line flag to explicitly enable Profiling similar to kube-controller-manager?

I'm not savvy to the tradeoffs of running this by default. I've read about security concerns, but we already expose a broad amount of metrics on :8080 and rely on Kubernetes networking to protect the pod. Perhaps there are some performance conerns?

Seems like it might be okay according to rakyll@
https://stackoverflow.com/questions/64057727/is-it-ok-to-use-golang-pprof-on-production-without-effecting-performance

[dewjam]

@ellistarn and I spoke offline a bit more and it's probably worth enabling the debug endpoint via a flag or ENV when needed.

[dewjam]

LGTM