kyechan99
[RFE] Create a cluster loader + pbench plugin.
Part of my desire in creating sonobuoy was to have a unified means of generating a performance report, that lived as a canonical thunk to be compared over time.
Combine cluster-loading + sonobuoy gathering + pbench data
/cc @jeremyeder @mffiedler @sjug
@carldanley @mauilion - Just as a PSA, something like this will eventually be needed todo scale out deployment validation
The blocker for this currently is that the pbench plugin needs the hostPID option on the pod which we dont surface.
I'm debating one of two approaches for this:
- in the plugin spec, allow the user to also provide an optional
podspecwhich will be merged with our templated version - dont surface any of this but, as #638 suggests, consume the plugin definitions on the clientside and produce the fully pods that we want to run (they'll be missing the call home info which will be added later though to report results). This approach ensures power users can do anything they want.
The downside of (2) is that it puts those power users back into the age of run sonobuoy gen -> edit file -> kubectl apply whereas (1) would allow the users to store those thanks in the plugin spec and still run with sonobuoy run --plugin foo and more easily support sharing of configs like that.
The blocker listed here is no longer relevant; there is not a PodSpec field on the plugin definitions which can override any of the default podspec settings.
There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.
@wilsonehusin I am marking this so that we can revisit this and prioritize for this year.
There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.