Chris Laprun

> Ok so was confused about OLM part, since it's not related to the core. But otherwise this makes completely sense. 👍🏼 > > just a note: for standalone workflows...

Personally, I think the SDK should focus on core functionality (and there's still a bit to do there) and leverage other tools fore additional support. Supporting RBAC/OLM generation at the...

It's also worth noting that some of that functionality could be addressed at the operator-sdk plugin level.

I was thinking about something like this, indeed, while I was thinking if there was a way to optimise managed fields-based matching (specifically, if we could somehow record the result...

Should we delete the branch as well, @csviri?

It seems to me that all this could be handled with appropriate pre-conditions… I'm also not sure if the workflow will keep being a DAG if we introduce this kind...

Would it make sense to have pre- and post-reconcile workflows that would get executed before and after calling the main reconciler method, respectively?

This is actually a multiple combination issue :) The core issue is in fact in the `operator-sdk` plugin and this is actually something I've been working on lately to clean...

Sorry for the ping-pong game but this indeed regards JOSDK and is not specific to the Quarkus extension. The problem is that, defining a namespace for your controller, means that...

?