Replies: 1 comment
-
|
Hello @rickraven! I'm Dosu, your friendly assistant here to help you tackle bugs, answer questions, and navigate the world of contributions. I'll be here while you wait for a human maintainer. Let's get your issue sorted out! 🚀 I couldn't find specific information on how Jaeger handles the 'insecure' and 'insecure_skip_verify' options in the codebase for Elasticsearch storage. However, the error message you're encountering suggests that the TLS verification is still being performed despite the configuration settings. One possible reason for this could be a misconfiguration or a bug in the version you are using. You might want to double-check the configuration file for any typos or incorrect indentation. Additionally, ensure that the Jaeger version you are using supports these options as expected. If the issue persists, consider checking for any updates or patches for Jaeger that might address this problem. You can also look into the Jaeger codebase to verify how these options are implemented and if there are any known issues related to them. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have jaeger 2.5.0 deployed as a singe file on vm (not docker/k8s). I specified elasticsearch as a backend storage and tried to disable tls checking.
My jaeger.yaml config file:
And after that I still have an issue:
Any ideas why check disabling doesn't work?
Beta Was this translation helpful? Give feedback.
All reactions