-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tempo-distributed] Update distributor proxy routes for GET 2.3.0. #2710
[tempo-distributed] Update distributor proxy routes for GET 2.3.0. #2710
Conversation
charts/tempo-distributed/values.yaml
Outdated
otlp/grpc: | ||
url: h2c://{{ template "tempo.fullname" . }}-distributor.{{ .Release.Namespace }}.svc:4317 | ||
otlp/http: | ||
url: http://{{ template "tempo.fullname" . }}-distributor.{{ .Release.Namespace }}.svc:{{ include "tempo.serverHttpListenPort" . }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The otlp/http ingest is separate from the tempo api, so we will end up with 3 distributor routings.
Distributor:url - tempo server listen port
otlp/grpc: 4317
otlp/http: 4318
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Have updated.
According to the Grafana Loki [documentation](https://grafana.com/docs/loki/latest/get-started/hash-rings/): * the query scheduler must be part of a hashring * the index gateway may optionally be part of a hashring This PR updates the chart such that the query scheduler and index gateway pods will expose the memberlist container port 7946, and include the member list selector label. The index gateway may optionally be prevented from joining the memberlist by setting `.Values.indexGateway.joinMemberlist` to false (default true), reflecting the current state of the documentation. Signed-off-by: verejoel <[email protected]> Signed-off-by: Sheikh-Abubaker <[email protected]>
GET 2.3.0 now includes functionality that allows the gateway to accept traces both via OTLP gRPC and HTTP. Also includes ability to define own proxy routes as a flag existed to enable this, but no configuration was available to set them. Signed-off-by: Heds Simons <[email protected]>
…P URL. Signed-off-by: Heds Simons <[email protected]>
Also includes ability to define own proxy routes as a flag existed to enable this, but no configuration was available to set them.