Todd Baert
Todd Baert
> I am querying whether there is a desire to have flagD as a provider the client SDK's can connect to is the goal. There's a definite interest internally at...
@xvzf I like this idea. I think maybe we should default to 2 instances. I think an additional config option makes sense, but I'm interested in the opinions of others......
Somebody mentioned this specific issue at KubeCon, so I guess you're right @xvzf
@heckelmann in your mind, would this co-exist with the annotation? Or would we remove that entirely?
@james-milligan suggested perhaps _using_ the label to add the annotation internally, which I think is a highly interesting approach, since we could roll it out without too many code changes...
> If I may, I would like to implement this ticket when we have a clear vision how it should work :) I can also try to prepare a quick...
Hey @rjdp . Great observation. It's entirely possible to stand up a single flagd that watches a number of CRDs and isn't injected into a workload pod, and then expose...
I think if Jaeger has a successful pattern it's not a bad idea.
I feel a bit conflicted. I can see arguments for both. Logically, the `FlagSource` CRD defines sources for flags - it's both an aggregation of `Flag` definitions, and a configuration...
You mean read-only access, I guess based on your use-case? I think I could be convinced of that. :thinking: