Add pprof profiling to the plain provisioner
Related to #266.
Goal: enable profiling for the plain provisioner.
AC:
- Update the plain provisioner's main.go executable package and add a pprof server.
When we do get to this, it'll be worth assessing the value add that enabling pprof profiling brings to our customer. In the context of existing OLM installations, the collect-profile pods have been a source of test failures/upgrade blockers in OCP, that raise alerts even though that functionality isn't used by the customer.
At the very least, if we do want something like this for engineering ease, we should discussing flags that can be toggled to enable this, with disabled being the default option.
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
This is a nice add to the RukPak project and is generally low-hanging fruit (hence the good-first-issue tag). However, we're not quite ready to devote team resources to get this done. If someone would like to get to this via a contribution please feel free to ask any question here!
In the mean time we'll reevaluate this at a later date.
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.