-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Clarification in docs #2038
Comments
It should not ignore CA, what makes you think it does? Meanwhile, this code will change with #1838 |
@yurishkuro well, when setting —es.tls I don’t see this line in that if path of the code: jaeger/pkg/es/config/config.go Line 308 in 4b58b94
But that’s only after I always had a “no such file or directory” - yes without a file path - error on startup. Removing the —es.tls flag, leaving behind the —es.tls.ca flag fixed the issue. So I checked the code and then came to the conclusion above. Although I didn’t check c.TLS.createTLSConfig() itself. |
The code does look strange and I think it could have a few comments, but when the CA path is set, both code branches will attempt to read the file. jaeger/pkg/es/config/config.go Lines 308 to 315 in 4b58b94
and jaeger/pkg/es/config/config.go Lines 344 to 360 in 4b58b94
|
@jpkrohling got it. It does make sense, although the jaeger/pkg/es/config/config.go Lines 308 to 315 in 4b58b94
Then my issue was definitely not having |
Hi everyone,
This line cost me 1 day 😄 ...
jaeger/pkg/es/config/config.go
Line 294 in 4b58b94
Maybe you could update to docs to be more specific in saying
--es.tls
ignores--es.tls.ca
? Or is it just me who got this wrong? 😊The text was updated successfully, but these errors were encountered: