Attila Mészáros

The original idea was, when we started to extract the samples, that we have just a few simple samples, that supports only the development maybe some quick checking / testing,...

That is true that is easier to upgrade them. So maybe the examples which are kind of showcases we should have in one repo. Question is what about the memcached,...

@adam-sandor you mean a separate repo with the samples, or directly to the SDK?

Ok, now I'm completely lost how you mean this, let's discuss it maybe on next weekly.

Was thinking about this, reading the actual state is already from the context: https://github.com/java-operator-sdk/java-operator-sdk/blob/464ca0262a9a296b3ea68fd1c59e18145ea1a296/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/AbstractDependentResource.java#L32-L32 It should be possible also to share event sources between dependent resources, in that case it...

Extracted the event source definition to this issue: https://github.com/java-operator-sdk/java-operator-sdk/issues/1514

We decided to park this issue intil v4 where this behavior will be the default.

see https://kubernetes.slack.com/archives/CAW0GV7A5/p1643798302258639?thread_ts=1643796946.554699&cid=CAW0GV7A5

@shawkins I added this to 3.3 milestone for now. To summarize it to my understanding there are two cases when running multiple instances of operators is happening and/or desirable, and...

> Maybe the strategy should be configurable i.e. the framework would support event replication but let users activate or deactivate it depending on their needs? Yes, a feature flag would...