-
Notifications
You must be signed in to change notification settings - Fork 635
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
new curator version breaks the TLS verify functionality #1708
Comments
Can you provide debug output of this, please? |
@untergeek Hi,
|
@untergeek had to retry with For some reason Elastic search config ignored the
|
No worries. Found it. Will have an update out shortly. |
Bump Curator version to 8.0.13 Fixes elastic#1708
Bump Curator version to 8.0.13 Fixes #1708
@rgaduput, I apologize for the inconvenience. This is totally fixed now in Curator 8.0.13, which has been published to PyPI and Docker as well (as untergeek/curator:8.0.13). Since you're using Kubernetes, you might be interested to know that you can avoid the |
@untergeek thanks for the quick check and the fix. |
When upgraded the curator from 8.0.8 to 8.0.10 we have observed that it fails to connect with Elastic with TLS exception even though cert verify is set to
false
, this functionality works just fine if we go back to older version 8.0.8.please note i have tried the latest version 8.0.12 as well.
Expected Behavior
Certs verification ignored while connecting to Elasticseach.
Actual Behavior
Fails to connect with below
Steps to Reproduce the Problem
Specifications
Context (Environment)
Trying to perform Elastic index clean up but ignore the certs while connecting to it since certs are self signed.
Detailed Description
The text was updated successfully, but these errors were encountered: