Steven Hawkins

> Unfortunately it's not that simple.. if that is set, the metadata.namespace of everything will be set to that value (which is not desirable. TLDR... it's bit of a mess...

> As far as I'm aware, it is possible to deploy your operator in separate pods and this scenario is supported by the OLM generator that allows you to generate...

> I think I'd need to see a more detailed explanation. In any case, this kind of change probably wouldn't happen before the next major version. I'm assuming there would...

> Lets pretend the ability to have quarkus deploy the Operator into the kluser is not even an option... I would want the quarkus folks to weigh in on that...

> I'm not sure these are two diffrent cases. The problem at hand is to be able to clearly define what is generated and to have a clearly define resolution...

> I think @metacosm is on the same boat with this one. Keep in mind that I'm advocated for not supporting any properties to individually override the controllers, nor for...

> I am really against the idea of having build time configuration which sets watched namespaces but can't be overrriden on runtime by any means. I am not suggesting that....

> This is not entirely accurate. Actually whether the controller is set to watch the current/single or all namespaces matters. Again, this is why I'm advocating for only using the...

> I still don't follow what you want the use of the annotation to be... Previously you talked about how it should be preferred during runtime... If the annotation \@ControllerConfiguration.namespaces...

> I've faced similar issues while trying to retrieve the logs too and not being able to do so until the pod became ready (which sometime never happens in case...