[GitHub] [camel-k] astefanutti commented on issue #2633: Camel-K Tracing Trait error

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

astefanutti commented on issue #2633:
URL: https://github.com/apache/camel-k/issues/2633#issuecomment-923752323


   > I think the reason why it does not get discovered is that the example from master creates the Jaeger instance in the "observability" namespace, while the tracing trait expects to find it in the current namesapce.
   
   We could search in all namespaces in that case, or search for namespaces with specific labels if there is such a convention.
    
   > I think we should go into a state like "Waiting for Bindings" (wdyt @astefanutti?), where we wait for other resources to be created before launching the integration. Currently we don't signal any error and just let the runtime to randomly log tracing errors.
   
   I agree it'd be better to act on missing requirements beforehand, rather than letting the runtime fail. We could introduce a `Pending` phase ("Waiting for Bindings" is going away with #2627), where all the pre-requisites would have to be satisfied before transitioning the Integration to the `Deploying` / `Running` phase, and each pre-requisite status would be reported as a condition. The problem I see with this approach is that it's a one time check, and the pre-requisites aren't monitored after that. Ideally, when a pre-requisite happens not to be satisfied anymore while the Integration is running, the operator should transition it to the `Error` phase, instead of letting it in `CrashLoopBackOff` state, that we know will fail. Which lead to the point where that `Pending` phase may not be really relevant, at least necessary, and it might be better to reuse the `Error` phase anytime a pre-requisite is not satisfied. WDYT?


-- 
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