Imagine that we have a SW that, receive events but don't send any event. (this is a potential valid SW)

When we work with a maven project, etc, to be able to deploy in kubernetes + knative, and work with the knative eventing system, etc., etc., we must include the kogito-addons-quarkus-knative-eventing   in our project.

At build-time, two resources are generated in our project  target/kubernets/knative.yml, and target/kubernetes/kogito.yml, all good.

This two resources contains the necessary information to produce the k8s deployment.

All good, now, when we look at the kogito.yml, we can see that several triggers and other components are like a SinkBinding declared

BUT it looks like for this particular case (see that SW don't produce any event, only receives) NO SinkBinding is generated.

Finally when we deploy the project in the situation above, the K_SINK health check introduced by the kogito-addons-quarkus-knative-eventing fails.

Why?

It fails because no SinkBinding was produced for that scenario. This is the bug.

We need to investigate a bit here, but at a first glance we have two options here:

1) if no SW produce events, the K_SINK health check shouldn't apply.

2) we always generate the SinkBinding, in the end, as soon we jump into k8s + knative eventing and  SWs which has events, we can assume that incoming and outgoing events can happen.