Update elasticsearch to 7.16.1 #58
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Do we want to take this opportunity to upgrade the kibana image as well? Apparently the images on Dockerhub are no longer supported. The new kibana docker image is located at |
|
I looked into it earlier today and saw quite a few breaking changes for Kibana. I'm not familiar with what we're currently using within Kibana and whether or not things would go south. |
|
Makes sense, let's leave Kibana for another day then. |
Zalgo2462
approved these changes
Dec 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #57
Updated the docker image for elasticsearch to 7.16.1. This also moves the build from pulling from DockerHub to pulling from elastic's docker registry.
Elasticsearch 7.16.1 takes care of the log4j vulnerability.
Tested on existing system with a Windows host feeding Kibana on BeaKer 0.0.8 and upgraded with no issues. Windows host continues to feed Kibana after upgrade.
There shouldn't be any caveats in upgrading clusters since BeaKer is single node.