gansheer opened a new issue, #4178:
URL: https://github.com/apache/camel-k/issues/4178
An auto discovery trait option exists in the `tracing` and `telemetry`
traits to discover automatically any Jaeger compatible service available. This
functionality (`tracing.auto` and `telemetry-auto`à is a quick shortcut for
basic usage:
* it only looks into the namespace of the integration
* build the endpoint with 'svc.cluster.local'
* look for a service containing:
* a `http-c-binary-trft` port and the label
"app.kubernetes.io/part-of=jaeger,app.kubernetes.io/component=service-collector"
for tracing
* a `grpc-otlp` port and the label
"app.kubernetes.io/part-of=jaeger,app.kubernetes.io/component=service-collector"
for telemetry
It then generated the valid endpoint if it found at least one service (on
the first found). If the Jaeger service is in another namespace it will not be
discovered.
It would be useful to be able to discover a Jaeger service present in
another namespace.
I see two ways to do that:
* search through all namespaces "available" (there are high impacts with the
security configurations in the k8s/OCP cluster)
* provide an option to indicate in which namespace the service can be found
like `trait.auto-namespace` (there are limited impacts the security
configurations in the k8s/OCP cluster)
Opening access to any other namespace service for discovery will mean the
operator need to be able to call some Kubernetes APIs, at least GET on service
Resources on the Jaeger namespace.
Note : `tracing` has been deprecated in 1.12.x and will most probably be
removed in 2.x but it has roughly the same code as `telemetry`.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
