Steven Hawkins

> Remove the @Deprecated annotation from SharedInformerFactory.inNamespace(). I'm assuming that the @Deprecated annotation means that the method will be removed in a future release, but I don't think it should...

> Should the entire SharedInformerFactory be deprecated based on the limitations that you mentioned? The class was added for compatibility with https://pkg.go.dev/k8s.io/client-go/informers#SharedInformerFactory - but note there that the namespace is...

@vmuzikar @mabartos test failure due to the erroneous warning should be addressed upstream. There are three more changes in this PR. However there is still an issue - the serialized...

> can multiple executions of onAdd method for example can happen simultaneously by different threads > execution of onAdd, onUpdate or onDelete can happen simultaneously by different threads (i.e. "add"...

> I'm wondering if this lines from the docs is relevant to the concurrency or it's regarding something else: http worker threads are a separately managed pool of threads, which...

There if you use one of blocking methods, then the informer won't be returned until after it has synced. > Also are you aware if there is a situation where...

This has been discussed / requested several times and there has been no strong work towards it. You can either: - advocate for a particular method(s) to have non-blocking counter-parts...

Relates to #40184

@KyriosGN0 it is. However we may need to give some thought on how this should be done in a controlled way, otherwise we're just moving the potential security risks of...

@KyriosGN0 For example setting the service account to be that of the operator, the keycloak pods would have the same privleges as the operator - which includes the ability to...