Thank you for the pointers. Let me take a look
On Friday, January 5, 2018 at 4:40:53 PM UTC-8, Daniel Smith wrote:
>
> The easy way is for the thing seeing the HW events to write to the
> "status" CR, and your observers watch the CR. But if I understand, you
> don't want to do that (data rate t
The easy way is for the thing seeing the HW events to write to the "status"
CR, and your observers watch the CR. But if I understand, you don't want to
do that (data rate too high?). So your other option is to make an
aggregated apiserver.
I think https://github.com/kubernetes-incubator/metrics-se
I'm trying to look at a design where I support a CRD of type "Status".
"Status" is updated based on HW Events. HW Events are known to the
controller side of the code. So, for "current state" I want the GETs to go
to the controller.
It may require a different URI for routing , I'm ok with that,
Can you give more detail? Are you trying to serve synthetic (manufactured)
data? Should these resources support verbs other than GET?
On Fri, Jan 5, 2018 at 11:05 AM, KG wrote:
> I have a scenario where certain CRD GETs need to be serviced from specific
> controllers. I don't want to use data fr
