Attila Mészáros

Hi @wangyushuai , the problem is that Kubernetes API does not support this, in Java Operator SDK this is supported, but just creating an informer for each namespace. Another option...

Ahh yes, forgot that, field selectors are also an option for namespaces, true.

Not in the current Informer implementation IMO, maybe an additional layer above it? It might make sense for other projects like the webhooks, where users tend also to implement Informers....

If some will need this to be configurable, we can just override it on our side. But having this defaulted to true is probably the expected way to go IMO.

See also discussions around here: https://discord.com/channels/723455000604573736/1032917332235911169/1212475397413928970

So, if I understand properly this would be kinda Group of dependencies, that can be used as a library in another project. Or more precisely a sub-workflow? > It would...

> > See also discussions around here: https://discord.com/channels/723455000604573736/1032917332235911169/1212475397413928970 > > Please post it here. Discord is opaque and we should be having these discussions here, not in some other service...

@metacosm could we pls discuss this under a different issue or GitHub discussion or on Discord :) this is not related to this issue. (but in general I agree that...

@emonical I think I understand what you mean, and see the point that the reusability of a group of dependents might bring some value. This is something that can be...

There is a plan to improve the builder, this can be also considered. cc @metacosm