Matthias Wessendorf
Matthias Wessendorf
/close all things are done, that are required
I think using the `core` one is fine, but it's not 100% clear to me why the CodeGen does generate the other one for `reactivex`. Question: should the Deserializer work...
I think I am not really sure we should add that to the `KnativeEventing` CR ... ``` apiVersion: operator.knative.dev/v1alpha1 kind: KnativeEventingSources ... ``` would be IMO a better separation? Also,...
> an alternative it to have one operator per event source. eg: https://github.com/openshift-knative/knative-kafka-operator that does _currently_ install both: Source and Channel, via one CR. We are looking to change that,...
I think that SERVING/EVENTING are more core, and more stable than "any random" source from contrib. So, not sure we should have all sources in the one and only operator...
So, the question really is ... do we want to have channel operators ? `eventing-operator` intalling "just" core... (does the IMC really cause any harm?) and per channel, one operator....
@lkingland any updates?
yes this would be super helpful
The actual link to the proposed GSoC idea: https://github.com/cncf/mentoring/pull/1159
See also https://github.com/knative/eventing/issues/7265