[GitHub] [camel-k] squakez commented on issue #3389: Propagate errors to KameletBinding status

[GitBox <gi...@apache.org>]

squakez commented on issue #3389:
URL: https://github.com/apache/camel-k/issues/3389#issuecomment-1209044273

   I had a look at this and I don't think it's a bug but the way it is designed the system so far (we may understand if it makes sense to change it though). Right now, if an `Integration` is in error state, then, the related `KameletBinding` is moved in error as well (tested with nightly build).
   
   The scenario illustrated is more generic because we never set an `Integration` in error when the traits are failing, but it is infinitely reconciled to watch for any change that may be applied to the `Integration` CR in order to have it fixed. That's the reason why we don't cascade the failure to the `KameletBinding`.
   
   We may reason if it makes sense to apply some retry logic (as we do for the `Build`) or at least report the failure in the `Integration` status, as it is really difficult to understand what's going on when this situation happen (until we check the operator log).
   
   Adding @astefanutti @lburgazzoli @oscerd to the thread for more opinions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org