You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[query] Use OTEL's helpers for grpc server (#6055)
<!--
!! Please DELETE this comment before posting.
We appreciate your contribution to the Jaeger project! ππ
-->
## Which problem is this PR solving?
- Towards #6026
## Description of the changes
- Migrates the GRPC query server to create the server using OTEL rather
than using a custom implementation
- Adds a log to warn users that having the same port for GRPC and HTTP
is now deprecated. We'll be removing this functionality after Feb 2025.
## How was this change tested?
- Unit tests / CI
## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
- for `jaeger`: `make lint test`
- for `jaeger-ui`: `yarn lint` and `yarn test`
---------
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]>
logger.Warn("using the same port for gRPC and HTTP is deprecated; please use dedicated ports instead; support for shared ports will be removed in Feb 2025")
108
+
}
103
109
tlsGrpc, err:=tlsGRPCFlagsConfig.InitFromViper(v)
104
110
iferr!=nil {
105
111
returnqOpts, fmt.Errorf("failed to process gRPC TLS options: %w", err)
0 commit comments