If a KameletBinding is invalid, the related status is not updated to report an error

[lburgazzoli]

Assuming a KameletBinding lacks sourece/sink, as example:

piVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: c82iernvdc4irh6evn20
  namespace: default
spec:
  integration:
    configuration:
    - type: secret
      value: c82iernvdc4irh6evn20
    profile: OpenShift
  steps: []

The operator will fail with something like:

{
  "level":"error",
  "ts":1644832192.1764352,
  "logger":"controller.kamelet-binding-controller",
  "msg":"Reconciler error",
  "name":"c82iernvdc4irh6evn20",
  "namespace":"cos",
  "error":"could not determine source URI: no ref or URI specified in endpoint",
  "errorVerbose":"no ref or URI specified in endpoint"
}

But the error is not reported in the KameletBinding's status

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[squakez]

This is similar to #3389 . The problem is that we don't set an upper limit for retries in the reconciliation loop (we probably do it only for the Build CR), so, this is left pending until the fix is applied. I wonder if we should immediately at least report the error condition or stop reconciliation when these kind of situations happen.