Attila Mészáros

Maybe just a separate module, within this project. Since it's called SDK, at least in my mind tool/libs for common subproblems fits. What do you think?

The thing is that the notification system might vary, based how the platform handles such events in a specific company, som might use kubernetes events others kafka messages to get...

Usually it works like this, companies have internal forks and internal builds of such open source projects (at least in my experience from multiple companies), where these extension points are...

I don't plan to work for now, will close and in case reopen later.

In general yes, but there is option also other way around in fabric8 if you prefer contract first approach.

For now I added sample and link for configuration and optional beans.

@michaelkoepf thx, yes this would be nice to have; do you plan to do a PR for this? it would great thx

Hi @Donnerbart , 1. I think we should iterate on that logging message, in some cases sure misleading, here where operator is registered: https://github.com/operator-framework/java-operator-sdk/blob/3723b1c8b72258583e260a40be298bce148c4daf/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/Operator.java#L240 it surely does not have configuration...

Regarding point 2 and 3. I think implementing a custom metrics interface, or extending the current implementation with micrometer, should do the job: https://github.com/operator-framework/java-operator-sdk/blob/3723b1c8b72258583e260a40be298bce148c4daf/micrometer-support/src/main/java/io/javaoperatorsdk/operator/monitoring/micrometer/MicrometerMetrics.java#L27 Note that you get callbeack when...

added pr for point 1: https://github.com/operator-framework/java-operator-sdk/pull/2891