Attila Mészáros

sure, currently its limited, since the dependent resources might have impact on this, for now see: https://github.com/java-operator-sdk/java-operator-sdk/blob/001cbaf38bc91332f0bced22649e3e7a465857ee/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/Context.java#L9-L13

> No this isn't at the moment. Maybe we should create a separate issue for this, and discuss where this should be done, not sure if this is quarkus extension,...

> Generally speaking, I think it's a bad pattern to expose the underlying implementation if we can avoid it. We switched from Watcher to Informer, we might switch to something...

Good question, I cannot think of a use case, since it's anyways our controller the logic of multiple might be merged to one reconciler. maybe for different versions?

> Would it be possible to add a label filter by configuration ? For those using config map as CRD it can help. That should be already possible, see: https://github.com/java-operator-sdk/java-operator-sdk/blob/5ad74190bd891cb4b184de35af748aff7d195175/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/ControllerConfiguration.java#L51-L51

thx @tonswieb we will take a look, it's quite strange, it look like the resource does not have metadata (from a quick look on the logs), will dig into it...

This might be better to have in fabric8 client also in our case. cc @manusa @shawkins

Are you sure about this? Maybe we should start by writing an Integration tests, since I don't see why it should not work.

This is a duplicate: https://github.com/java-operator-sdk/java-operator-sdk/issues/1175

Closing this since its a duplicate.