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 too high?). So your other option is to > make an aggregated apiserver. > > I think https://github.com/kubernetes-incubator/metrics-server is the > best existing example of one. Service catalog also uses one. > > https://github.com/kubernetes-incubator/apiserver-builder might be a good > way to get started. > > If you want to support watch with a non-etcd backend, that may not be easy. > > On Fri, Jan 5, 2018 at 4:22 PM, KG <gunji...@gmail.com <javascript:>> > wrote: > >> 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, but I want >> to be able to bypass the etcd. >> >> >> >> >> On Friday, January 5, 2018 at 12:30:46 PM UTC-8, Daniel Smith wrote: >>> >>> 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 <gunji...@gmail.com> wrote: >>> >>>> I have a scenario where certain CRD GETs need to be serviced from >>>> specific controllers. I don't want to use data from etcd. Are there any >>>> examples I can refer to? >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Kubernetes user discussion and Q&A" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to kubernetes-use...@googlegroups.com. >>>> To post to this group, send email to kubernet...@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/kubernetes-users. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Kubernetes user discussion and Q&A" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to kubernetes-use...@googlegroups.com <javascript:>. >> To post to this group, send email to kubernet...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/kubernetes-users. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
