Expose dev config in Operator
In case of VM testing on OpenShift, where RAPL is not available, we can make use of fake-cpu-meter config. Right now, it's not being exposed as part of the default config. Should we do it just for our testing purposes? Thoughts?
cc: @KaiyiLiu1234 @sthaha
How would this work in practice? Could you please elaborate how this hack will be used in testing if there aren't any RAPL zones detected?
Just having the config available as the Default config in the configmap should be sufficient. No need to expose in spec. Whoever wants to use fake readings can just edit configmap and set the flag as true.
closing as #510 addresses this