nicolaferraro commented on issue #2633: URL: https://github.com/apache/camel-k/issues/2633#issuecomment-923041921
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. In these cases, you need to set the tracing endpoint manually, like: ``` kamel run -t tracing.enabled=true -t tracing.endpoint=http://simplest-collector.observability.svc.cluster.local:14268/api/traces hello.groovy ``` Or whatever endpoint is your tracer listening to. 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. -- 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
