Skip to content
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

gateway: make tempo-query forwarding on gateway optional #705

Merged
merged 6 commits into from
Jan 16, 2024

Conversation

frzifus
Copy link
Collaborator

@frzifus frzifus commented Dec 1, 2023

Closes #628

@frzifus frzifus self-assigned this Dec 1, 2023
@frzifus frzifus force-pushed the allow_gateway_without_jaeger_ui branch from 1aaeba2 to b13b0ee Compare December 1, 2023 16:26
@frzifus frzifus changed the title gateway: make jaeger-ui forwarding optional gateway: make tempo-query forwarding on gateway optional Dec 1, 2023
@frzifus frzifus marked this pull request as ready for review December 1, 2023 16:27
@@ -410,6 +518,11 @@ func TestTLSParameters(t *testing.T) {
},
},
Template: v1alpha1.TempoTemplateSpec{
QueryFrontend: v1alpha1.TempoQueryFrontendSpec{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why this change?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To not break the test. Previously the trace.read.endpoint was configured even when tempo-query was disabled.
The alternative would be to remove:

assert.Contains(t, args, fmt.Sprintf("--traces.read.endpoint=https://%s:16686",
	naming.ServiceFqdn(tempo.Namespace, tempo.Name, manifestutils.QueryFrontendComponentName)))

@frzifus frzifus force-pushed the allow_gateway_without_jaeger_ui branch 3 times, most recently from 35b13ac to 625b194 Compare December 20, 2023 17:47
@frzifus frzifus force-pushed the allow_gateway_without_jaeger_ui branch from 625b194 to 5d60c07 Compare December 21, 2023 08:50
@frzifus frzifus force-pushed the allow_gateway_without_jaeger_ui branch from 5d60c07 to 1708c1b Compare January 16, 2024 09:26
@codecov-commenter
Copy link

codecov-commenter commented Jan 16, 2024

Codecov Report

Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (b077f89) 0.00% compared to head (49057da) 77.66%.

Files Patch % Lines
internal/manifests/gateway/gateway.go 73.91% 4 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff            @@
##           main     #705       +/-   ##
=========================================
+ Coverage      0   77.66%   +77.66%     
=========================================
  Files         0       68       +68     
  Lines         0     5157     +5157     
=========================================
+ Hits          0     4005     +4005     
- Misses        0      954      +954     
- Partials      0      198      +198     
Flag Coverage Δ
unittests 77.66% <73.91%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Signed-off-by: Benedikt Bongartz <[email protected]>
@frzifus frzifus merged commit a2023c1 into main Jan 16, 2024
11 checks passed
@frzifus frzifus deleted the allow_gateway_without_jaeger_ui branch January 16, 2024 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot enable gateway while disabling jaeger ui
3 participants