Add a setup script and according makefile target to upgrade ES keystore from older versions of ES #120
Conversation
This file contains 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
BendingBender
changed the title
…re from older versions of ES
BendingBender
force-pushed
the
add-setup-script-to-upgrade-keystore
branch
from
78715d8 to
302166d
Compare
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.
What does this implement/fix? Explain your changes.
When upgrading the stack from ES 8.13.x (and older) to newer versions of Elasticsearch, the generated keystore becomes incompatible. ES then tries to migrate the keystore automatically, but in the container the keystore is mounted via the secrets system and can't be moved or changed (a bind mount would experience the same problem). Elasticsearch then simply refuses to start.
This PR adds a setup script that manually runs the keystore migration in an independent container.
Does this close any currently open issues?
no
Any relevant logs, error output, etc?
no
Any other comments?
no
Where has this been tested?
locally