-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[query] Change HTTP and TLS server configurations to use OTEL configurations #6023
[query] Change HTTP and TLS server configurations to use OTEL configurations #6023
Conversation
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6023 +/- ##
==========================================
+ Coverage 88.60% 96.90% +8.30%
==========================================
Files 349 349
Lines 18158 16599 -1559
==========================================
- Hits 16088 16086 -2
+ Misses 1888 329 -1559
- Partials 182 184 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
@yurishkuro would you be able to re-run the CI? getting some docker failures |
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
pkg/config/tlscfg/options.go
Outdated
@@ -142,6 +142,28 @@ func (o *Options) ToOtelClientConfig() configtls.ClientConfig { | |||
} | |||
} | |||
|
|||
// ToOtelServerConfig provides a mapping between from Options to OTEL's TLS Server Configuration. | |||
func (o *Options) ToOtelServerConfig() configtls.ServerConfig { | |||
cfg := configtls.ServerConfig{ |
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.
what about translating Enabled to Insecure?
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.
@yurishkuro The Insecure
field doesn't actually exist on configtls.ServerConfig
, it only exists on configtls.ClientConfig
(see https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configtls/configtls.go#L112-L126). The TLSSetting
field in configgrpc.TLSSetting
and confighttp.TLSSetting
is a pointer type so setting it to nil implies no TLS/ insecure (see https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configgrpc/configgrpc.go#L168-L171).
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.
I changed this method to return a pointer and return nil when !o.Enabled
.
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
@yurishkuro what did we want to update here? |
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>
if it's still accurate then nothing, I thought maybe with this refactoring there might be changes |
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.
🎉
Oh I see. Yeah no changes required here because we didn't touch the CLI interface - just the internals of where the configs were being held. |
I think this might be a breaking change if we are switching from internal TLS management to OTEL's because our internal |
Which problem is this PR solving?
Description of the changes
reload_interval
s rather than immediately on file changes. This makes Jaeger's behavior similar to OTEL Collector's behavior.How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test