Attila Mészáros

> > > I'm not sure I follow you. There is no pattern for this in JOSDK since there are no specific event sources for external resources. > > >...

> The use case I'm talking about and that isn't covered is where a dependent is a kubernetes dependent (in this case a Secret) so extends KubernetesDependentResource but needs to...

Hi @vladimirionescu , thx for reporting, note that this is already fixed for upcoming v5. https://github.com/operator-framework/java-operator-sdk/blob/e9bafc7fb766ac2c8240e536d2a2775dd54cd1bb/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/event/source/informer/Mappers.java#L62-L78

This sounds, useful yes! Note that you can now add arbitrary information to the context and use it later when creating the status here: https://github.com/operator-framework/java-operator-sdk/blob/7e2f3aecece65a9ef1a5999e2785888ae458837b/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/dependent/managed/ManagedDependentResourceContext.java#L26-L41

I think we should add this to all conditions, and the functionality directly to `Condition`. What do you think, @metacosm ?

> The problem with adding it to all conditions is that we will need to rethink how results are reported since the conditions are more or less invisible at this...

Would make sense IMO, I can imagine that as part of `SSABasedGenericKubernetesResourceMatcher`, that could also log this information. Do you plan to also create a PR?

sure, pls do! thx!

It would be good to handle such cases in the framework, unfortunatelly the current SSA Matcher is not prepared for that. But would be nice to do such experiments, and...

This is more an issue for fabric8 client. cc @manusa @shawkins