-
Notifications
You must be signed in to change notification settings - Fork 5
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
Elasticsearch 6.x EOL #162
Comments
I agree we should update the Elasticsearch 7.x. Updating the Elasticsearch package probably is not too much work. |
Keep in mind that in Amsterdam we currently only have an Elastic cluster running version 6 at our disposal. So if this package needs to be updated in the python code we need to check if we can also update the elastic cluster in Amsterdam. This is something we currently do not have under our own control. |
Maybe it's time to upgrade the Elasticseach version, since Elasticsearch ships with Log4j > 2.9.0 since version 6 :) |
@martijncalker for your information I found this update on the issue on the elastic discuss https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476 We are looking into this. |
Elasticsearch 6.8.21 released with a fix: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/release-notes-6.8.21.html |
Hi there,
Currently the Helm Chart depends on Elasticsearch ~6.8.0. The 6.8 version of Elasticsearch has been EOL since 2020-11-20.
The application depends on the Python Elasticsearch package, which is only compatible with Elasticsearch 6.x.
Are there any plans on upgrading Elasticsearch to a supported version?
The text was updated successfully, but these errors were encountered: