Pires

>* operator get_pods(all_namespace) >* check if an operator is already running You lost me here. This provides no guarantees whatsoever. And looking into pods is not enough. You'd have to...

Going back to your argument of the current behavior being a huge limitation: > When I'm saying a `huge limitation`, it's not that huge... it's just annoying to be forced...

As a maintainer, I want to make sure this software is easy enough for anyone to use and be successful. Given the description of your requirement, which seems irrelevant to...

@Quentin-M thank you for putting things in a different perspective and for sharing a way to achieve this, which is pretty neat. However, it requires building and pushing the operator,...

@supriya-premkumar thank you for this contribution. Following #126, would you be open to work with me to evolve this PR into something that doesn't depend on having users building their...

Can I find you on NATS slack, @supriya-premkumar? Ping me @pires! Thanks a lot.

The limitation here is that this requires users to build their own binaries/container images. I also think this would not work as expected given https://github.com/nats-io/nats-operator/blob/master/cmd/operator/main.go#L108-L112

NATS protocol requires direct connectivity to peers when trying to establish routes. With Istio, you are introducing a proxy (actually, two!) in between peers. You shouldn't do that! Since I'm...

As mentioned to @wallyqs privately, I think it's best for everybody if we keep both NATS and NATS-Streaming _operators_ as one. After all, NATS needs to be in place for...

There has been a lot of work on the structure of the code, so we can have one operator _to rule them all_, instead of maintaining separate repos. I'll be...